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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior, so the description need not restate those. It adds useful behavioral detail beyond annotations: exact pins are checked exactly, ranges are resolved to today's install-pick version, and problems are listed first.

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 tight, front-loaded sentences: the first names the action and scope, the second states version-resolution semantics and output ordering. Every sentence earns its place with no filler or repetition of the schema.

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 two-parameter read-only tool with a 100%-documented schema, rich annotations, and an output schema, the description provides everything needed to call it correctly: input expectations, version-checking semantics, scope, and result ordering. No critical behavioral gap remains.

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 value by listing the accepted manifest filename patterns (package.json, requirements*.txt, pyproject.toml, etc.) and clarifying that content is the full file text. This goes beyond the schema's generic 'e.g. package.json' example.

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?

The description clearly states the tool checks every dependency in a manifest file's text and enumerates supported manifest formats, giving a specific verb and resource. It does not explicitly distinguish itself from the sibling check_packages, though the 'manifest file's text' framing makes the scope inferable.

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?

There is no explicit guidance about when to use this tool versus get_advisories or check_packages. The supported-format list implies it is for manifest-file inputs, but no alternative is named or excluded, leaving the agent to infer the decision.

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

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context beyond these: the 100-package limit, the specific checks performed, the verdict categories, and the version-omission behavior. No contradiction with 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?

The description is two sentences with no filler. It front-loads the core action and scope, then lists verdicts, and ends with a concise parameter tip. Every sentence earns its place.

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?

Given the annotations, output schema, and the description's coverage of limits, verdicts, and version behavior, the tool is sufficiently specified for an agent to invoke correctly. The only notable gap is the lack of explicit routing guidance relative to sibling tools, but this does not block correct usage.

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 only 50%, with only ecosystem described as 'Registry.' The description compensates by clarifying that packages are checked for existence, latest version, deprecation, advisories, licence, and age, and by explaining that omitting version checks the latest. This adds meaning beyond the raw 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?

The description clearly states a specific action ('Checks up to 100 packages in one registry') and enumerates the checks performed and verdicts returned. It is easy to understand what the tool does, though it does not explicitly differentiate itself from sibling tools like check_manifest or get_advisories.

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?

The title 'Check packages before installing' implies when the tool should be used, and the description adds operational guidance like 'Omit version for the latest.' However, there is no explicit statement of when to prefer this tool over siblings or when not to use it.

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

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description only needs to add behavioral context. It does so by stating the version default ('latest if omitted') and enumerating the response contents, including advisory metadata and the count affecting the latest version. No contradiction with annotations is present.

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?

The description is a single sentence that packs in the action, scope, default behavior, and output contents without filler. Every clause earns its place and the most important scoping detail appears early.

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?

The output schema exists, so return-value details are already structured, and annotations cover the safety profile. The description adds the key usage nuance (version defaults to latest) and the advisory fields returned. A minor gap is that it does not explicitly distinguish when this tool should be preferred over check_manifest or check_packages, but the overall definition is sufficient for correct invocation.

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 only 33%, so the description carries some burden for parameter meaning. It adds genuinely useful semantics for the version parameter ('latest if omitted') and describes output fields, but it does not clarify the meaning of name or ecosystem beyond what the schema's enum and property name already imply. This is partial compensation rather than full coverage.

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?

The description uses a specific verb ('Lists') with a clear resource ('known security advisories') and scopes it to one package version, defaulting to latest when omitted. It also enumerates the returned fields, making its purpose distinct from the sibling tools, which appear to target manifest or package checks.

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?

The description clearly conveys when the tool applies: when a caller needs security advisories for a specific package version, with latest as the default. It does not explicitly state when not to use it or name alternatives, but the context is strong enough for an agent to select it correctly.

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