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

Beyond the annotations, which already declare this as a safe read-only idempotent operation, the description discloses important behavior: ordering, returned fields, status values, the 15-minute timeout-to-failed rule, account-wide visibility, filter semantics, and the caveat that an empty page means no matches for the filters rather than no Diagnostics existing.

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 front-loaded with the purpose and packs useful information into a compact paragraph. The long sentence enumerating returned fields and statuses is dense but justified because there is no output schema; overall it avoids filler.

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 list tool with no output schema, the description is highly complete: it explains what is returned, status values, ordering, visibility, filters, pagination edge-case meaning, and example use cases. An agent has enough information to call it correctly without needing more context.

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 covers limit and cursor clearly, but client_id has no schema description; the tool description compensates by explaining it filters to one client workspace. It also reinforces the meaning of since and connects empty pagination results to filter semantics. Limit and cursor behavior are left largely to the 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 states a specific verb and resource: it lists Diagnostics in the connected Yellowhead account. It adds scope details like newest-first ordering and account-wide visibility, but it does not explicitly distinguish this list tool from the sibling get_diagnostic tool.

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?

It gives clear usage context through example questions such as 'what Diagnostics do we have' and 'is my Diagnostic ready', and notes that it can help find two runs to compare. However, it does not explicitly say when to use get_diagnostic instead, nor does it state any exclusions.

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