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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds that results include risk/run/grant state and confirmation location, which is useful payload context, but says nothing about pagination via limit/cursor or the wait_seconds long-poll behavior.

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 compact sentence, front-loaded with the verb and resource, with no filler. The list-after-colon construction is slightly telegraphic but wastes nothing.

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 6 undocumented parameters, no output schema, and a schema that mixes list controls (limit/cursor/status) with single-record lookup (approval_id) plus polling (wait_seconds), the description leaves the tool's core calling modes unexplained. That is a substantial gap for a read tool that clearly has two distinct invocation shapes.

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% across 6 parameters, so the description must compensate and does not. It never mentions workspace, the status enum (pending/decided/all), approval_id for single-record fetch, limit/cursor paging, or wait_seconds, leaving the agent to infer list-vs-single mode from bare field names.

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 ('approvals') and enumerates the fields surfaced (risk, run, grant state, where to confirm). It does not explicitly contrast with the sibling approvals_decide, though 'Read' implicitly signals a non-mutating counterpart.

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 or when-not-to-use guidance, and the alternative (approvals_decide) is never named. 'Where to confirm them' gestures at the decision flow but gives no condition that tells an agent to call this rather than the decide tool.

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