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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond them — that only task participants can retrieve this result — which is an authorization constraint, though it says nothing about error behavior for non-participants or the shape of the result.

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?

It is short, but this is under-specification rather than conciseness — the entire text is a title echo with no front-loaded explanation of what is returned. There is nothing to trim and nothing that earns its place as 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?

For a read-only getter with one undocumented parameter and no output schema, the description leaves the agent without the essentials: what a verification result contains, what happens for non-participants, and how it relates to preview_verification. The output schema's absence puts the burden on the description, which does not carry it.

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 0% and the single required parameter task_id is undocumented in both schema and description. The description adds no meaning about which task's verification is returned, what a valid task_id looks like, or whether it must be one the caller participates in.

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?

Tautological: description restates name/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 parenthetical '(participants only)' is the sole usage signal, implying an access restriction, but it is not framed as a when-to-use rule. There is no guidance on when to call this versus preview_verification, check_task_spec, or get_task.

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