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

Annotations already indicate destructive action (destructiveHint=true), but the description goes further: it explains irreversibility ('cannot be undone'), the real-world consequence (sends to a real council/parking operator), the payment step, and the requirement to show the checkout_url rather than falsely claim success. This provides substantial behavioral context beyond annotations.

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?

The description is concise yet information-dense. It front-loads the core purpose, then covers irreversibility, payment flow, required fields, and user instruction in a logical order. Every sentence serves a purpose, 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 mutating, irreversible action with a payment component, the description covers side effects, prerequisites (name/address), the conditional payment step, and the expected output (checkout_url) and subsequent automatic filing. It is sufficiently complete for an agent to invoke correctly without an output schema.

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 schema documents id, name, and address, with descriptions for name and address (67% coverage). The description adds value by explaining that name and address are required for the appeal but can be sourced from the profile if not passed, and clarifies the required condition. This goes beyond the schema's minimal description of the parameters.

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 verb ('files') and resource ('the drafted appeal'), and clarifies it is done in the account holder's name. It also differentiates from siblings like 'lookup_appeal_status' by implying this is the actual filing action, not a status check. The purpose is unmistakable.

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 provides clear context on when to use it (filing a drafted appeal) and includes critical pre-conditions like 'confirm with the user first' and the payment flow for unpaid notices. It does not explicitly name alternative tools, but the context strongly implies when not to use it (e.g., for checking status), so it is clear enough.

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