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

Goes well beyond the annotations: discloses that deletion is deferred behind a confirmation token, that referenced addresses leave the address book but persist on orders/quotes, that the last address cannot be removed, that the newest remaining address becomes default, and that a signed-in account is required with a sign-in prompt otherwise. That is exactly the kind of side-effect and auth context annotations cannot carry.

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?

Five tight sentences, front-loaded with the two-phase behavior and the return values, then the edge cases. Dense but no filler; only the printdash.io domain reference is slightly redundant.

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?

Output schema exists and the description still names what comes back (summary + confirmation_token). Combined with the auth requirement, the last-address guard, and the default reassignment rule, an agent has everything needed to invoke this and follow up with confirm.

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 description coverage is 0% and the description never names address_id or explains its format, only referring to 'one saved address' and 'the only saved address'. The sole parameter's semantics are left entirely to the bare schema, which is a real gap even though the parameter is a simple ID.

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 and resource ('Prepares deleting one saved address') and immediately frames it as a two-phase operation returning a summary and confirmation_token. This is clearly distinguishable from create_address, update_address, and list_addresses in the sibling set.

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?

Explains the required follow-up ('Nothing is deleted until confirm is called with it after the customer agrees'), an explicit exclusion (the only saved address cannot be deleted, use create_address first), and the default-address side effect. When-to-use and when-not-to-use are both covered with a named alternative.

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