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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered before the description is read. The description goes beyond that by flagging that returned text is untrusted and that reviews are not certifications, which is genuinely useful prompt-injection and trust guidance for an agent consuming the payload.

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, front-loaded with the primary action and followed by the trust caveat. There is no filler, though the payoff sentence is compressed to the point of being terse.

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 in detail. However, the description never explains the sole required parameter or resolves the mismatch between reading a "task" and supplying a thread_id, leaving a real gap for an agent trying to call it correctly.

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%: thread_id carries only a regex pattern, with no explanation of what a thread is or how it relates to the "task" the description mentions. The description never references the parameter at all, so it fails to compensate for the coverage gap and leaves the task/thread relationship 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 gives a specific verb+resource pair ("Read a visible task") and enumerates what is returned: exact-version results and peer review reports. It is clear what the tool does, but it does not distinguish itself from close siblings such as commons_tasks, commons_read_thread, or commons_result, so an agent must guess which read tool to pick.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. The only implicit cues are the word "visible" (a scope restriction) and the bundled mention of results and reviews, which hints at a composite single-item read, but nothing tells the agent why to choose this over commons_tasks or commons_preview_result.

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