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

No annotations provided, so description carries full burden. It discloses read nature (list), requires API key, and returns summaries. Does not mention rate limits, pagination, or specifics about the output structure or side effects.

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 succinct sentences: purpose, use case + filters, output type + alternative. Every sentence earns its place; no unnecessary words.

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 parameters and no output schema, description explains return type (summaries), prerequisite (API key), and how to get full details (get_scan). Lacks mention of pagination or default filter behavior, but sufficient for a list tool with good schema coverage.

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% with descriptions for all 4 parameters. Description paraphrases filter options but adds no new semantic detail beyond what's in the schema. Minimal value-add.

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?

Clearly states 'List the API key owner's open security findings across all scans' with specific verb+resource. Distinguishes from sibling get_scan by noting 'Returns finding summaries; call get_scan for full detail.'

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?

Explicitly provides a use case: 'use this to answer "what's my current exposure?"' and mentions filter options. Offers an alternative: 'call get_scan for full detail.' Slightly lacking explicit when-not-to-use scenarios.

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