Strong foundation with 10 well-named, read-only tools backed by clear descriptions and structured input schemas. All tools follow verb_noun naming (depsdev_get_*, depsdev_find_*). Descriptions are concise (50-200 chars) and explain WHAT and WHEN. Input parameters have types and descriptions. However, output schemas are inferred from Go struct tags rather than explicitly documented in the MCP schema registration, limiting LLM visibility into response structure. No pagination support despite tools that could return large result sets. Error handling is basic, no recovery guidance or actionable error messages visible in the code.

• Add explicit output schema documentation to each tool's MCP registration. Document the Output[T] wrapper structure and the fields of each T (e.g., Package.versions, Version.licenses, Dependencies.nodes). Use JSON Schema to make response structure machine-readable.
• Implement pagination for depsdev_get_package and depsdev_get_project_package_versions. Add limit (default 20, max 100) and offset/cursor parameters. Return total_count and next_cursor in responses. Document in tool descriptions: 'Returns up to 20 versions; use offset to fetch more.'
• Define 'system' as an enum constraint in the JSON Schema for all 6 tools that use it: ['go', 'rubygems', 'npm', 'cargo', 'maven', 'pypi', 'nuget']. This prevents invalid ecosystem values and self-documents valid options.
• Enhance error messages with recovery guidance. When validation fails (e.g., invalid ecosystem), return: 'Invalid ecosystem: got "nodejs", must be one of: go, rubygems, npm, cargo, maven, pypi, nuget.' When a package is not found, suggest: 'Package "react" not found in npm. Try depsdev_query() to search by version key or hash.'
• Expand depsdev_query description to explain the query language. Document supported fields (versionKey.system, versionKey.name, versionKey.version, hash.sha256, etc.), provide 2-3 realistic examples, and note any query length limits or rate constraints.