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

Annotations already flag destructiveHint=true, and the description goes further by specifying 'immediately' (no grace period), what is destroyed ('active grants and pilot sessions'), and what is untouched ('the provider or other consumers'). That is real added value beyond the annotations, though the unexplained 'Private draft' marker muddies whether behavior is final and whether the action is reversible.

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 destructive action front-loaded, but the leading 'Private draft:' fragment is unexplained noise that competes with the actual action verb for the reader's attention.

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 values need no explanation, and the annotations carry the safety profile. Still missing for a destructive one-parameter tool: what projectId identifies, whether the revocation is idempotent or reversible, and what happens to in-flight invocations.

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?

The single parameter projectId has 0% schema description coverage, so the description must carry its meaning — but it never mentions projectId, instead speaking of 'this account' and 'one provider API.' An agent must guess how projectId maps onto the described scope, which is a genuine gap in a destructive tool.

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: 'immediately revoke this account's active grants and pilot sessions for one provider API.' It also bounds the blast radius ('does not affect the provider or other consumers'), which implicitly separates it from provider-wide operations, though it never names the nearby siblings request_provider_access or cancel_provider_access_request.

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?

There is no when-to-use/when-not-to-use guidance and no explicit routing to alternatives such as cancel_provider_access_request, which an agent could easily confuse with this tool. The only hint is the scope statement about other consumers, which describes effect rather than usage conditions. The 'Private draft:' prefix also raises an unanswered question about whether the tool is safe to invoke at all.

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