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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so safety is covered. The description adds only the vague 'documented defaults' clause and a block/run targeting statement that does not correspond to any parameter, which is more confusing than informative.

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 short sentences with the core purpose front-loaded, which is good. However, the 'omission uses the documented defaults' sentence spends space without conveying usable information.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What is missing is any parameter guidance for three undocumented fields and a coherent explanation of the block/run targeting behavior, which is the main practical gap for an agent trying to call this tool.

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 0% for three parameters (limit, query, status), so the description carries the full burden and provides no semantics for any of them. The mention of targeting a block/run does not map to any actual parameter, leaving limit's cap, query's scope, and status's enum values unexplained.

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 gives a specific verb and resource ('List user tests') plus what is returned ('IDs and status'), which is enough to separate it from get_test and get_test_progress. It is slightly muddied by the claim that it can 'target a block/run', which no listed parameter supports.

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 references list_test_blocks as a source of IDs but never states when to choose this tool over get_test, get_test_progress, or list_test_blocks itself. 'Omission uses the documented defaults' points at documentation that is not provided, so no real usage condition is established.

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