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

Goes well beyond the annotations: it explains that readOnly here means no remote contact, that 'Completed' only means a response was recorded rather than a verified business effect, that the provider payload is bounded and untrusted, and that a withdrawn grant/session/module right yields denial. That trust and authorization framing is exactly the context an agent cannot get from readOnlyHint/openWorldHint.

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?

Four dense sentences, front-loaded with the scope and exclusions, with no filler. Some clauses ('Attempted and ambiguous never authorize replay') are compressed to the edge of ambiguity, which slightly hurts readability without wasting words.

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?

For a single-parameter read tool with no output schema, it covers what is returned (operation, approval state, provider response), how to interpret 'Completed', and the denial condition. The remaining gap is the identifier itself — nothing tells the agent where a valid operationId comes from or what happens with a stale one.

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 parameter with 0% schema description coverage; only a regex pattern conveys anything, and the description never mentions operationId, its origin (presumably from prepare/execute), or how to handle an unknown/expired id. With low coverage the description needed to compensate and 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 (the operation / approval state / bounded provider response) with an explicit scope limit: 'only this tenant/user/current OAuth grant's operation.' The phrase 'Does not contact the remote server, retry, approve or execute' separates it from the execute/prepare siblings without needing their names.

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?

Clear context for use: read the recorded outcome of an operation scoped to the caller's grant, with explicit exclusions (no contact, no retry, no approve, no execute) and the rule that attempted/ambiguous states never authorize replay. It does not name the sibling (e.g. execute_remote_mcp_tool) that would be used instead when a call must actually be made, leaving that inference to the agent.

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