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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description carries a lighter burden. It adds the useful behavioral constraint that the job must be completed and that the result is 'MCP task-compatible,' but it does not disclose what happens for incomplete jobs, error behavior, or the response envelope.

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 a single, front-loaded sentence with no filler. Every word contributes either to what the tool returns or the precondition that the job is completed.

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-only getter with full schema coverage and safety annotations, the description is largely sufficient. The absence of an output schema makes the vague phrase 'MCP task-compatible final result' a minor gap, and there is no discussion of the not-yet-completed case, but the agent still has enough to invoke the tool correctly.

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 parameter semantics are already fully documented in the schema. The description adds no additional meaning about taskId or includeJob beyond what the schema provides, making the baseline score of 3 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 states a specific verb ('Return') and a clear resource: the final result of a completed durable ATA research job. It is distinctly a result-retrieval tool, but relies on the phrase 'final result' rather than explicitly naming how it differs from sibling tools like ata_get_research_task or ata_get_research_job_status.

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?

Usage context is implied by the word 'completed': the tool is for finished research jobs, not in-progress ones. However, there is no explicit when-to-use guidance, no exclusion of alternatives, and no mention of when to prefer a sibling getter such as ata_get_research_task or ata_get_research_job_status.

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