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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is disclosed. However, the description adds no additional behavioral context—it never mentions irreversibility, cascading effects, permissions, or consequences of deleting a location. It simply restates the action without enriching what annotations already provide.

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 a single, terse sentence with zero wasted words. It front-loads the action and is appropriately sized for a simple delete operation.

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 basic delete with one parameter, the description, schema, and annotations together convey the essential information. It lacks explicit statements about permanence or side effects, but given the simplicity of the operation, this is adequate yet not rich.

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% and the locationId parameter is documented with 'Location ID'. The description does not add any extra meaning or format details beyond this, so the baseline 3 is appropriate since the schema fully covers the parameter.

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 'Delete a saved location' uses a specific verb and resource, making it immediately clear what the tool does. It distinguishes from sibling location tools (add, list, nearby) because deletion is the only destructive operation among them.

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 no guidance on when to use this tool versus alternatives, such as whether to verify the location exists first or if there are any restrictions (e.g., cannot delete a location referenced by other entities). No context is given for prerequisites or when to prefer other trip-related tools.

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