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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds no behavioral context beyond the schema; it does not indicate what the response contains, whether a missing ID returns an error, or how this fits into the export workflow.

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?

A single sentence with zero wasted words, and the action 'Get' plus the resource 'Clarity export run' are front-loaded. This is appropriately concise.

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 simple read tool this is close, but with no output schema and no mention of what is returned or how the ID is obtained, an agent cannot fully predict the call's behavior. It should reference startClarityExport or listActiveClarityExports for 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?

With 0% schema description coverage, the description needed to compensate for the id parameter's meaning. Saying 'by ID' adds little beyond the schema, and it does not clarify that the ID comes from starting a export or listing active exports.

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 ('Get a Clarity export run by ID'), making the lookup intent clear. However, it does not explicitly differentiate this from sibling tools like listActiveClarityExports or getRun, so it falls just short of a 5.

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?

No guidance is provided on when to use this tool versus startClarityExport or listActiveClarityExports. There is also no mention of prerequisites, such as obtaining an export run ID first.

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