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

Annotations already declare this as destructive and not read-only. The description adds useful behavioral detail beyond annotations: it cancels a pending Charter reservation and cannot release an engraved signature. It does not explicitly state irreversibility, though the destructive annotation covers part of that.

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 compact sentences front-load the core action and then add side effects, exclusions, and the required confirmation constraint. Every sentence carries useful information with no filler.

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 opt-out tool with no output schema, the description covers the main action, side effect, exclusion, and required confirmation. It leaves return behavior implicit, but the annotation already signals destructive behavior.

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 50%, with the token parameter fully described in the schema. The description compensates by specifying that confirm must be true, which is essential semantics for the otherwise undocumented required boolean parameter.

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 states a specific action and resource: giving back the Pioneer number on Pedra as an opt-out. It also clarifies a key scope boundary, that an engraved signature cannot be released here, though it does not name sibling tools directly.

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?

It clearly indicates when to use the tool (to opt out/give back the Pioneer number) and notes the side effect of canceling a pending Charter reservation. It also states an exclusion (engraved signatures cannot be released here), but does not name an alternative tool for that case.

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