Prepare ReceiptCal account deletion

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false. The description adds useful scope ('permanent', 'server-side data'), but does not clarify the staging semantics — whether calling it deletes anything, how long the staged state persists, or whether it must be paired with confirm_action. The 'permanent deletion' wording sits in mild tension with destructiveHint=false, though 'Stage' keeps it from being an outright contradiction.

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?

A single front-loaded sentence with no filler; the staging intent and the affected scope are stated immediately.

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 zero-parameter staging tool with no output schema, the description is usable but incomplete: it omits what 'staged' means operationally (confirmation requirement, cancellation, expiry, reversibility) — the most important context for a deletion-intent tool.

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?

Zero parameters and 100% schema description coverage, so there is nothing for the description to disambiguate. Baseline 4 applies for a no-parameter 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 ('Stage') and resource ('permanent deletion of the authenticated ReceiptCal account and its server-side data'), so the agent knows exactly what is being prepared. It is clear but does not explicitly differentiate itself from the confirm_action/cancel_action workflow or from other prepare_* siblings.

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 word 'Stage' implies a two-phase flow, but the description never says when to call this versus alternatives, that a later confirmation is required to actually delete, or that the staged action can be cancelled. No prerequisites, exclusions, or alternative tools are named despite confirm_action/cancel_action being siblings.

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