Remove Address Book Entry

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

Annotations already flag destructiveHint=true, and the description adds value beyond them: the removal is permanent, the entry type is restricted on paid/owner-authorized entries, and each call costs 1 credit. The credit cost and the API-vs-Pro restriction are behavior facts an agent cannot get from structured fields.

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?

Three compact sentences, front-loaded with the action, then the eligibility restriction, then the confirm and credit-cost constraints. Nothing is padding.

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 two-parameter tool with full schema coverage and no output schema, the description covers eligibility, confirmation, and cost. Only minor gaps remain, such as what happens to entries with dependent snapshots or bundles.

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 100% and the schema already documents both 'address' and the confirm-must-be-true boolean. The description repeats the confirm requirement without adding format or validation detail, so it does not meaningfully exceed the schema.

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 ('Remove an address from the address book'), which cleanly separates it from the sibling rename tool and from the bundle-address tools that operate on a different resource.

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 explicit when-you-cannot-use-it guidance: paid-plan entries or owner-authorized entries must be handled in Octav Pro instead of the API. It does not name a sibling as an alternative, but the exclusion condition is concrete enough to prevent a wrong call.

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