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

Annotations only flag this as destructive, non-idempotent and open-world; the description goes well beyond by disclosing that state is rechecked immediately before the call, that a completed call returns an unverified provider report rather than proof of effect, that ambiguity means unknown outcome, and that an unresolved call blocks the whole connection. It also warns that returned content is untrusted data, not instructions.

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?

Front-loaded with the action and precondition, then tightened with short declarative constraints ('No retries.', 'Attempted or ambiguous means unknown outcome'). It is dense with specialized vocabulary but every sentence carries operational weight; only the final untrusted-data sentence is boilerplate-adjacent.

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 destructive, non-idempotent, no-output-schema tool this covers the essential hazards: no retry, unknown-outcome semantics, connection blocking, and unverified results. What remains unstated is how to look up an operation's status afterwards or which sibling yields a valid operationId, leaving recovery after failure underspecified.

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 0% for the single operationId, and the description never states its origin, format, or that it must come from a prior preparation/approval. It does implicitly characterize the parameter as an opaque reference to an already-scoped operation by listing everything rechecked under it (tool, endpoint, credential version, config, OAuth, authority), which is real added meaning but not full compensation.

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?

The description pairs a specific verb ('Execute') with a narrow resource: 'only an own current-grant operation' that was approved or covered by a standing grant, resolved to 'one MCP tools/call or exact reviewed HTTP request'. That is far more specific than the name alone and separates it from a prepare step, though it never names the prepare/list siblings 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?

Preconditions are stated with unusual precision ('after exact owner browser approval or a current bounded standing grant') and exclusions are explicit ('No retries', 'never change requestKey or resubmit to repair it'). What is missing is routing guidance to the sibling that produces an operationId or the one that reports outcomes, so the agent must infer the workflow.

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