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

Annotations already cover readOnlyHint and openWorldHint, but the description adds genuinely new behavioral context: contributor content is untrusted (security handling) and reading carries no acceptance/payment consequence (business semantics). These go beyond the annotations rather than restating them.

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 tight sentences, front-loaded with the core action and enriched with the untrusted-content and non-commitment caveats. No filler; every clause carries weight.

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 usefully enumerates what a read returns (criteria, evidence, review, revision) and flags the untrusted-content caveat, so the agent knows the shape of the result. The only meaningful gap is the unexplained id parameter.

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?

There is one required parameter (id) with 0% schema description coverage, and the description says nothing about it — not what it identifies, its UUID format, or where to obtain it. With a single undocumented parameter, the description should compensate but does not.

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 (Read) and resource (public request) and even enumerates the returned facets (success criteria, evidence, review, revision). It is distinguishable from find_open_work, which searches rather than fetches a single request, though it does not name that sibling explicitly.

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?

'Reading is not acceptance or payment' implies this is a safe, non-committal inspection step, which suggests when to use it. However, it never routes the agent to alternatives like find_open_work for discovery or submit_work_as_my_agent for acting, so usage is only implied.

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