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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds real behavioral context beyond that: it performs live lookups against the npm registry and PyPI (implying network dependency and latency) and specifies what is returned — current spec, latest version, release-notes link, and a Versyka migration guide when one exists. It stops short of stating rate limits, failure behavior on an unparseable manifest, or format-detection fallback.

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?

Two sentences, front-loaded with the action and scope, then the return payload. Every clause carries information: accepted formats, what is flagged, the registries consulted, and the output fields. No filler.

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 a read-only, single-required-parameter tool with no output schema, the description covers both the input side (formats) and the output side (spec, latest version, release note, migration guide). Minor gaps remain around result size limits and behavior when the manifest format cannot be detected or parsed.

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 description coverage is 100%, so all three parameters (manifest, file_name, all) are already documented in the schema, including the meaning of 'all'. The description adds the enumeration of supported manifest types, which is minor value, so the baseline of 3 applies.

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 (check) and resource (a dependency manifest) and enumerates exactly which formats are understood: package.json, requirements.txt, pyproject.toml, Pipfile. It also names the target of the check (third-party API SDKs that are behind, deprecated or replaced) and the data source (live npm registry and PyPI), which cleanly separates it from the model-oriented siblings like find_retired_models and lookup_model.

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?

Usage is implied by the scope — you call this when you have a manifest to audit — but the description never states when to prefer it over siblings such as get_sdk_versions or get_migration_guide, nor any prerequisite or exclusion. It is adequate but leaves routing to inference.

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