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

Annotations already convey readOnly, idempotent, and non-destructive behavior, so the description carries a lower burden. It usefully adds that this targets platform-managed workflows and is scoped to the bound case study, but it does not disclose response shape, status meanings, or pagination behavior. No contradiction with annotations.

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?

One tightly constructed sentence with no filler. The primary use case is front-loaded, and the secondary mode is appended in a single clause.

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 read-only polling tool, the two main usage modes are stated and the annotations cover safety. However, with no output schema and two parameters lacking meaningful description, an agent cannot fully determine the role of researchRunId or whether caseStudyId must correspond to the bound case study. Slightly incomplete for a 4-parameter 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 only 50%, and the description only adds meaning for workflowJobId (via its omission behavior) and 'bound case study' context for caseStudyId. researchRunId remains completely unexplained, and includeResult's behavior is only stated in the schema, not the description. The description does not compensate enough for the undocumented parameters.

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 uses specific verbs ('Poll', 'list') and identifies the exact resource ('platform-managed research workflow') and the key selector (workflowJobId). It clearly distinguishes the two invocation modes and does not merely restate the title.

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 provides clear usage conditions: pass workflowJobId to poll a specific workflow, or omit it to list recent workflows for the bound case study. It does not explicitly mention when to prefer sibling tools like ata_get_research_job_status, but the core call pattern is unambiguous.

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