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

Annotations already establish readOnlyHint=true, idempotentHint=true and non-destructive, so the safety profile is covered. The description adds real context beyond that by defining this as a poll and by naming the terminal states ('succeeded', 'failed') and their handling. It omits intermediate states and polling cadence, which keeps it from a 5.

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?

Three short sentences, no filler, and the core action ('Poll...') is front-loaded. Each sentence adds a distinct operational instruction.

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 described, and the description covers the two terminal branches well. It is slightly incomplete for a polling tool because it doesn't mention in-progress/pending states or how long to wait before re-polling.

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%. study_id and job_id carry no descriptive text, and the description never explains what the job identifier represents or how it is obtained (presumably from queue_customize_study). Only organization_id has schema documentation, so the description leaves most parameters unexplained.

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?

States a specific verb and resource: 'Poll a queued study customization turn.' The polling role is clear and implies it pairs with queue_customize_study. It does not explicitly name sibling alternatives, so an agent must infer the workflow boundary, but the purpose itself is unmistakable.

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?

Gives outcome-based instructions: on succeeded call get_study, on failed inspect the saved study before retrying. This is concrete workflow guidance with named next steps. It does not address when polling is unnecessary or distinguish this from get_participant_job/get_report_job, so it stops short of the top tier.

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