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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the 'compact' qualifier, which hints at the output being a summary rather than full data, but it does not disclose other behaviors like response format, pagination, or rate limits.

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, front-loaded sentence with no filler. It conveys the purpose and key parameter in six words, making it extremely efficient and easy to parse.

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 simple one-parameter, read-only tool with an output schema, the description is nearly complete. It clearly states what the tool does, and the 'compact' descriptor sets expectations. It could be improved by mentioning typical use cases or what the summary includes, but this is adequately covered by the output schema.

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?

With 0% schema description coverage, the description compensates by explaining that scan_id is the identifier used to fetch the summary. It adds meaning beyond the schema's bare type/name, though it stops short of providing format constraints or examples.

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 verb ('Get') and resource ('compact scan summary'), and identifies the lookup key ('by scan_id'). This distinguishes it from sibling tools like get_scan_result or get_scan_reports by emphasizing the 'compact summary' aspect.

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 implies the tool is for retrieving a condensed overview of a scan, but it does not explicitly state when to use it over alternatives or mention any exclusions. Given the large sibling list, the lack of explicit guidance limits its usefulness for choosing between similar get_* tools.

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