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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The word "Poll" usefully implies an async job that must be re-checked, but the description never says what states are possible, whether it can still be running, or how completion is signaled.

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, clearly front-loaded with the action and then the follow-up. Nothing is wasted, though the terseness is partly responsible for the documentation gaps noted elsewhere.

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. But for an async polling tool the description should convey job lifecycle (pending/running/done), polling cadence, and where job_id comes from; none of that is present, so an agent cannot fully use it without guessing.

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 coverage is 50%: organization_id is documented in the schema, but job_id (the required parameter) has no description anywhere. The description adds no meaning about what job_id refers to, where it comes from, or the admin-only semantics of organization_id, leaving the required parameter's origin to inference.

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 says "Poll a participant batch," which conveys that this retrieves status for an asynchronous batch-creation job, and the name reinforces it. However, "participant batch" is vague and it never explicitly says this returns job status/progress, nor does it distinguish itself from siblings like get_participant or get_report_job.

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 gives one concrete chaining instruction (on success call list_participants to get invitations), which is genuinely useful workflow context. But it omits when to call it at all, how often to poll, or how it relates to create_participants versus other job-status siblings.

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