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

Annotations only declare readOnlyHint=false, so the description carries most of the burden and does it well: it discloses that this is a gate, that the underlying action must be re-invoked with approval_id, and adds a safety caution ('Never claim execution before the call succeeds'). It does not cover expiry, denial handling, or what the returned approval_id looks like, but the workflow and caution are genuine value-add.

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, zero filler, with the core purpose front-loaded ahead of the follow-up flow and the caution. Every sentence earns its place.

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-value explanation is unnecessary, and the description fully captures the request-review-then-resubmit loop plus the no-premature-claim rule. It leaves minor gaps around denial/expiry behavior, but nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% and the schema already documents tool_name, arguments (including the approval_id exclusion), and summary. The description reinforces the 'same arguments plus approval_id' contract but adds no format or syntax detail beyond the schema, so the 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: 'Request review of an exact policy-gated MCP action.' This is clearly distinct from siblings like agent.approvals.list or agent.actions.next, which neither request nor gate anything. An agent can identify the tool's role without opening the schema.

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?

Provides clear context: use this when an action is policy-gated and needs human review, and explains the follow-up ('After approval call that same tool with the same arguments plus approval_id'). It does not explicitly name alternatives or state when approval is NOT needed, so it stops short of full when/when-not guidance.

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