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

Annotations already declare destructiveHint=true and openWorldHint=true; the description adds value beyond that by stating what is NOT affected (existing payments are untouched) and that the state is reversible via enable. It also surfaces the underlying endpoint, but does not mention idempotency of repeated disables or error behavior for an already-disabled request.

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 a 'WRITE:' marker, then effect, reversibility, side-effect scope, and endpoint in roughly two sentences. No filler and nothing an agent needs is buried.

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 state-change tool with no output schema, the description covers the mutation's effect, its reversibility, and the blast radius (existing payments unaffected). Combined with annotations that flag it as destructive, an agent has everything needed to call it safely.

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?

Only one parameter and schema description coverage is 100%, so the pattern and required-ness are fully documented by the schema. The description adds no extra meaning about the id format or where to obtain it, so 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 (disable) plus resource (payment request) and the concrete effect: the link no longer accepts payments. It explicitly distinguishes itself from instamojo_enable_payment_request, so an agent can separate the pair without opening either 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?

Clear usage context: use it to stop a payment link from accepting payments, and the reverse operation is named. There is no explicit 'when not to use' guidance (e.g. versus deleting or letting it expire), but the selection signal against the sibling is unambiguous.

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