Delete ship-from address

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

Annotations already flag destructive=true, but the description adds genuinely new consequences: existing purchased labels are unaffected, at least one address is always retained, and the default is never deleted. These are exactly the side-effect and precondition details an agent needs beyond the hints.

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 prohibition on deleting the default is front-loaded correctly, and the four short sentences are easy to scan. There is mild redundancy, since 'the default address cannot be removed' is restated later as 'never deletes the default'.

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 one-parameter destructive tool with full annotation coverage and no output schema, the description covers the important constraints and the blast radius. It doesn't say what a failed delete returns (e.g., invalid or default id), which is a minor remaining gap.

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 the schema already documents it at 100% coverage, including the pointer to list_ship_from_addresses. The description adds no syntax or format detail beyond that, so the baseline of 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 and resource ('Removes a saved Ship From Address') and scopes it to Settings, which cleanly separates it from create/update/list_ship_from_addresses and set_default_ship_from_address. An agent can identify the operation without opening the 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?

Gives an explicit precondition/exclusion: the default address cannot be removed and another address must be made default first, which implicitly routes to set_default_ship_from_address. It doesn't name that sibling tool explicitly, keeping it short of a 5.

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