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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a bit of context with 'durable' and 'task-compatible facade,' hinting that this returns task projections rather than raw jobs, but it does not explain behavior such as ordering, pagination, or the meaning of the projection.

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 concise sentence and gets to the action immediately. It is not bloated, and the opening word 'List' is an appropriate front-loaded verb. However, some phrasing like 'MCP task-compatible facade' is jargon-heavy and could be clearer without adding length.

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 tool with six optional parameters, low schema description coverage, and no output schema, the description leaves too much unspecified: return shape, default limit behavior, filtering semantics, and how this relates to other ATA job/task tools. The annotations clarify safety but not usage or results, so the definition is only minimally adequate.

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 only 17%, with five of six parameters undocumented. The description does not compensate: it mentions 'recent' but does not clarify limit, jobType, activeOnly, caseStudyId, or researchRunId. The only parameter described in the schema, includeJobs, carries the explanatory burden alone.

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 names a specific resource ('recent durable ATA research jobs') and a clear action ('List') through a distinctive 'MCP task-compatible facade.' This is more specific than a tautology and gives some sense of scope, though it does not explicitly differentiate itself from sibling tools like ata_get_research_task or ata_list_research_reports.

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?

The description gives no guidance on when to use this tool versus the many sibling list/status tools. It only implies that this is for recent durable jobs, but does not mention alternatives, exclusions, or when a different tool like ata_get_research_task or ata_get_research_job_status would be more appropriate.

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