delete_locator

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

With no annotations, the description carries the full burden of disclosing behavior. It merely states 'Delete a locator' without mentioning that deletion is destructive, irreversible, or has side effects. No information about error handling or confirmation is provided.

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 extremely short and to the point, but it includes a parameter listing that largely repeats the input schema. The single sentence 'Delete a locator' is useful, while the parameter line adds little value, making it slightly less concise in information density.

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 simple one-parameter delete tool, the description is too sparse. It does not explain what a locator is, what happens after deletion, or whether the operation can be undone (especially given the presence of an 'undo' sibling). The absence of annotations and output schema makes this description inadequate for a complete understanding.

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 description adds a basic explanation for the only parameter ('Index of the locator to delete'), which clarifies the schema's minimal 'Locator Index' label. However, this is only a slight improvement and lacks detail about valid ranges, required format, or behavior if invalid.

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 tool's action ('Delete a locator') with a specific verb and resource. It is distinct from sibling tools like create_locator or get_locators, though it doesn't explicitly differentiate beyond the obvious deletion action.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., undo, create_locator, get_locators). The description lacks any context about prerequisites, conditions, or scenarios where deletion is appropriate.

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