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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: results come in upstream default order, no sorting support, hasMore semantics, and guidance to prefer narrowing filters over paginating. This goes beyond the 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 sentences with no waste. The key behavioral guidance (newest first, filter over paginate, no sorting, hasMore semantics) is front-loaded, and the nextPageToken guidance is concise. Every sentence earns its place.

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?

Complete for a list tool. The output schema exists, so return values are covered. The description covers ordering, pagination semantics, filtering guidance, and the annotations cover safety. Nothing an agent needs to call it correctly is missing.

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 the schema already documents all 7 parameters. The description adds context for the filter parameters (status, batchId, fileNameContains) and the pagination behavior, but doesn't add much beyond what the schema descriptions already provide. Baseline 3 is appropriate.

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 the tool lists recent parse runs, newest first, and identifies the resource as parse group. It distinguishes itself from sibling list tools by specifying the parse-run resource and the 'newest first' ordering, which is a specific behavior.

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 advises filtering over paginating, states that sorting is not supported, and explains when to use nextPageToken ('only when every item is needed'). This gives clear guidance on when to use this tool and how to behave, though it doesn't name a specific alternative tool.

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