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

Annotations already establish this as a safe, closed-world read, so the description is free to add the details that matter: the response is the complete item body and carries the contentHash that approve_item depends on. That downstream coupling is real behavioral context an agent could not infer from the annotations, though return format/pagination specifics are left unstated.

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 tight sentences with the core action first, then the workflow constraint. Every clause carries information — what it returns, why it matters, and what it feeds into — with no restatement of the title or schema.

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?

There is no output schema, so the description must convey the return value, and it does: the full item content plus the contentHash. Combined with the approval workflow framing, an agent has everything needed to call this correctly and use the result.

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% and the single id parameter already documents its origin ('from list_pending_approvals or get_briefing'). The description adds no further syntax or format guidance for the id, so the schema does the heavy lifting and 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 and resource ('Read one item ... in full') and scopes it to a single item, which cleanly separates it from list_pending_approvals and list_conversations. It also names what the payload represents ('exactly what approving it would publish, send or change'), so the agent knows what kind of content comes back.

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?

Gives explicit sequencing guidance: fetch the full item and show the owner before calling approve_item, and notes the contentHash is required for approval. It does not explicitly state when not to use it (e.g., browsing many items), though the singular 'one item' plus the id source in the schema implies list_pending_approvals for enumeration.

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