delete_location

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

Annotations already set destructiveHint=true, but the description adds valuable context: the operation is permanent (irreversible), readers need reassignment, and the subscription updates automatically. These side effects go beyond the mere destructive flag, giving the agent a clearer picture of consequences.

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 description is two sentences, front-loaded with the core action, and immediately follows with the most critical caveat and side effect. Every word contributes value, with no redundancy or filler.

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 tool with one parameter and no output schema, the description covers permanence, side effects (reader reassignment), and automatic subscription updates. This is sufficient for an agent to understand the full impact of calling this tool without ambiguity.

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?

The schema covers 100% of the parameter description ('Location ID to delete'), so the description does not need to add parameter details. The description mentions associated readers but does not tie that to the id parameter specifically, so it adds little beyond what the schema already provides.

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 clearly states the action: 'Delete a location permanently.' It specifies the resource (location) and the action (delete), and the permanence distinguishes it from update_location. It also differentiates from sibling delete tools by referencing location-specific side effects like reader reassignment.

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 description provides clear context that this tool is destructive and should be used with caution, but it does not explicitly state when to use it versus alternatives like delete_template or update_location. It implies the use case (permanent removal of a location) but offers no exclusions or alternative routes.

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