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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only the legacy-support note and ID sourcing, leaving return/pagination behavior unexplained (though an output schema exists).

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, front-loaded with the core action and free of padding. The only weakness is that the second sentence's default-omission clause is misleading rather than helpful.

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?

With an output schema present and annotations covering the read-only profile, the description needn't explain returns. Still, for a tool with an ambiguous name amid many get_test_* siblings, it should state how it differs and reconcile the required testId with the 'omission' claim; those gaps leave the agent under-informed.

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% on a single required parameter, so the description must carry the load. It does identify the ID source (list_test_blocks) and implies a block/run identifier, but the statement that omission 'uses the documented defaults' directly conflicts with testId being required, muddying rather than clarifying the parameter.

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 ('Read test summary and status by ID'), which is clear on its own. However, it does not differentiate itself from closely named siblings like get_test_progress or get_test_definition, which an agent would need to disambiguate.

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 partial guidance by pointing to list_test_blocks as the ID source and noting legacy support, which is useful context. But it offers no when-to-use versus the get_test_* siblings, and the 'omission uses the documented defaults' claim is unusable because testId is required by the schema.

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