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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable behavioral caveats beyond the schema—the moving registry default, possible null ossfScore on unverified mirrors, system case-lowering, and resolved dependencyCount. This enriches the agent's expectations without contradicting 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?

Three dense sentences deliver purpose, return fields, and critical usage caveats with no filler. Every sentence earns its place, and the most important operational warning (version pinning) is emphasized inline.

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?

Despite having no output schema, the description enumerates the main return fields, notes the null-scorecard edge case, and covers optional parameter behavior. Combined with rich annotations and fully described parameters, this gives an agent enough context to invoke the tool correctly.

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. The description goes further by explaining the semantics of omitting version (moving target, potential null scorecard) and clarifying that system is lowercased server-side, adding real value over 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 specifies the exact resource ('project insights') and enumerates concrete outputs (OSSF scorecard, repo stars/forks, advisories), making it clearly distinct from sibling tools like get_vulnerabilities or get_package. The verb 'Get' is paired with a well-scoped resource, earning full credit for purpose clarity.

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?

Clear context is provided: this tool gives health/security insights for a package's source project via deps.dev, with specific guidance on pinning versions for a stable scorecard. It does not explicitly name alternatives or when-not cases, so it falls just short of a 5.

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