Delete a subscriber's location

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds genuine value beyond them by naming concrete blast radius (delivery, audience membership, published data, irreversible state) and the confirm gate, though the consequences remain hedged with 'may affect' rather than specified precisely.

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?

Two short sentences with zero filler; the action is front-loaded and the consequence/precondition detail follows. Nothing needs to be trimmed.

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, non-idempotent tool with full schema coverage and no output schema, the description covers the action, its risk, and the required confirmation flag. It stops short of explaining what a caller should expect after deletion (e.g., resulting state or reversibility mechanics), leaving a small 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?

Schema description coverage is 100%, so account, confirm, and subscriber_id are all documented in the schema itself. The description only restates the confirm requirement and adds no new semantics (e.g., what happens if confirm is omitted), so the baseline 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?

The description opens with a precise verb+resource statement ('Delete a subscriber's location'), which is self-evidently distinct from the neighboring update_subscriber_location and pin_subscriber_location tools. An agent can tell what this does 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?

It states the precondition 'Requires confirm=true' and warns of side effects, which implies the action should only be taken deliberately, but it never names an alternative (e.g., update_subscriber_location) or states when deletion is the right choice over updating. Usage is implied rather than spelled out.

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