list_scans

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which inform safety. The description adds that it returns a slim summary per scan with specific fields and is ordered newest first, but does not disclose additional behavioral traits like permissions or side effects beyond what annotations provide.

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 very concise: two short paragraphs and a bulleted list for arguments. It front-loads the main action and includes necessary details without fluff. Every sentence adds value.

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 simple nature of the tool (list with pagination), the description covers the purpose, output summary, pagination, and pointer to the sibling tool for full data. The annotations confirm read-only and idempotent behavior. An output schema exists, so the description does not need to detail return values. All relevant context is provided.

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?

The input schema has 0% description coverage, so the description compensates fully by explaining each parameter: 'limit: Maximum number of scans to return (default 20)' and 'offset: Pagination offset into the scan history (default 0).' This adds clear semantics beyond the raw schema types.

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 'List InBody scans with headline metrics, newest first.' It identifies the verb (list), resource (scans), scope (headline metrics), and ordering (newest first). It also distinguishes from sibling tools by mentioning get_scan for full metrics.

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 explicitly guides the agent to use get_scan for full metric set, providing an alternative. It explains the limit and offset parameters for pagination. However, it does not explicitly state when not to use this tool, but the context is clear.

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