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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that this is an asynchronous poll and that a succeeded job yields result_url, which is useful behavioral context, but it omits terminal/error states and polling cadence.

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?

Two short sentences with zero filler; the core action is front-loaded and the follow-up pointer is second. Nothing is wasted.

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?

An output schema exists, so return values need not be spelled out, yet the description still references result_url. For a 3-parameter tool with 33% schema coverage and no annotation of failure modes, the description is adequate but leaves the job-status lifecycle and two undocumented parameters unexplained.

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 33% (job_id and study_id carry no description beyond uuid format), and the description adds nothing about any parameter's meaning, format, or constraints. With low coverage the description should compensate and does not.

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 verb (poll) and resource (asynchronous report request), and explicitly distinguishes this tool from get_study_report by naming it as the follow-up step. An agent can tell it apart from generate_report/get_study_report without opening any schema.

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 clearly places the tool in a workflow: poll a job, and once the job has succeeded, use get_study_report to retrieve the result. The usage context is explicit, though it does not state what to do on a failed/pending job or how frequently to poll.

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