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 contributes only the 'asynchronous task' framing; it says nothing about polling cadence, task expiry, or terminal vs. in-progress states, which are the behavioral details an agent actually needs here.

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?

A single tightly worded sentence with the resource and scope front-loaded and zero filler. Appropriate sizing for a one-parameter, read-only lookup.

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?

With no output schema, the description is the only place that could explain possible status values (pending/running/succeeded/failed) and whether the task result is retrievable here or elsewhere. That gap matters for an async status tool, though the call itself is simple enough that the definition is still workable.

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 100%, so the single task_id parameter is already fully documented with its origin ('returned by a previous verification request'). The description adds no format, length, or validity information beyond the schema, so the baseline 3 applies.

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 ('Get') and resource ('current status of an asynchronous verification task'), which is unambiguous and clearly distinct in kind from sibling list/stats tools. It does not explicitly name how it differs from get_verification_history or get_verification_stats, but the 'status of a task' framing is specific enough to route correctly.

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?

No when-to-use statement, prerequisite, or alternative is given. The reader must infer from the word 'asynchronous' that this is a polling call made after a prior verification request — and that dependency is only spelled out in the schema's parameter text, not the description.

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