Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description's final 'read-only' line is redundant with annotations, but it adds genuinely useful behavioral context beyond them: auto-detection of ecosystem, one-task-per-call semantics, version-specific result specificity, output reading order (summary and hint first, then inspected fields), and next_calls follow-up behavior. It does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Long and dense, but it stays front-loaded and every sentence earns its place: the core purpose, trigger list, ordering constraint, task semantics, parameter rules, output-handling protocol, examples, and exclusions are all instruction-bearing. The trigger list is somewhat long and some phrases overlap with the install-ordering sentence, but the structure is clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter tool with no output schema, the description leaves little unaccounted for. It states the exact task enum semantics, the version/from_version pairing rules, the auto-detection behavior, how to read the result (summary and hint first, then relevant data fields), and the next_calls follow-up flow. The only moderate gaps (e.g., exact return format) are mitigated by the described output-reading protocol.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic value: it warns to pass the public registry package name, not an import path or repository path; specifies which task requires which version (package version with check/security, from_version with upgrade/migrate/debug); gives concrete argument examples for express and next; and adds 'set ecosystem for ambiguous non-npm names' with 'set the ecosystem for non-npm names ambiguous.' This goes meaningfully beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: verify a public registry package before installation, recommendation, or dependency changes. Names multiple concrete scenarios (safety, CVEs, typo/slopsquat, deprecation, breaking changes) and explicitly differentiates from siblings (not for find_code, not for get_installed_dependencies), so an agent can distinguish it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit ALWAYS trigger list (install, add package, upgrade, bump, migrate, is this package safe, check CVEs, etc.), a strict ordering rule (call before npm/pnpm/yarn/bun/pip/cargo/gem install; do not install first and inspect later), and a preference statement over web search and raw registry metadata. Also names when NOT to use it (installed dependencies, locale nding code). This is comprehensive and non-ambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.