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

Annotations are all false (not read-only, not idempotent, not destructive), so the description carries the burden. It discloses who can act, the state precondition, refusal cases for invalid ids/statuses, and the return value. This goes well beyond the bare schema, though it doesn't detail the resulting state transition (e.g., status changes to 'withdrawn') or error response format.

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 sentences, each earning its place: action plus rationale, constraints/refusals, and return value. The content is front-loaded with the core purpose and the examples are brief but helpful. No fluff or procedural repetition.

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 tool with no output schema and all-false annotations, the description is complete: it states the action, who is allowed, the valid state, what gets refused, and what is returned. An agent has enough to decide when and how to invoke it correctly.

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 input schema already provides 100% coverage with a detailed description of 'id'. The tool description adds extra meaning by tying 'id' to the 'pending' status and clarifying that anyone else's id is refused. This reinforces and extends the schema, adding the state constraint that isn't present there.

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 opens with the specific verb 'Cancel your own pending access request', which precisely names the action and resource. It also distinguishes this tool from siblings like resolve or create by emphasizing 'own' and 'pending' – an agent can immediately tell what this tool is for.

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?

The description gives clear when-to-use context with examples ('no longer need the tool, or you got access another way') and explicit when-not conditions: only the requester may withdraw and only while pending, with refusal for other states. It doesn't explicitly name an alternative tool like resolve for handling others' requests, but the exclusion constraints make the boundary unambiguous.

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