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

No annotations are present, so the description carries the full behavioral burden. It discloses the return shape (findings with severity and remediation) but says nothing about whether the scan is read-only, what data leaves the environment, how the archive inputs interact with the zero-required-parameter signature, or what happens if no input is supplied.

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?

Three short, front-loaded sentences with the resource scope stated first and the return value last. The middle sentence is a positioning claim rather than operational information, but it is brief and does aid selection.

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 scanner with no annotations and no output schema, the definition covers purpose and rough return content but leaves important gaps: what is scanned when no parameters are supplied (all params optional), and how archive_url and archive_base64 relate to each other. Adequate but incomplete.

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 (ecosystems, archive_url, archive_base64) are already documented in the schema. The description adds no syntax, precedence (archive_url vs archive_base64), or format detail beyond that, so the baseline 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 (scan) and concrete resource set (package manifests, lockfiles, MCP server configs) targeting supply-chain compromises, and claims a distinctive scope (MCP config as a security surface). It does not explicitly distinguish itself from the sibling dependency_check, so it stops short of a 5.

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 stated scope implies when the tool applies (auditing manifests/lockfiles/MCP configs for compromises), but there is no explicit when-to-use/when-not guidance and no mention of dependency_check as the nearest alternative. Routing is left to inference.

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