delete_locator

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does not state whether deletion is permanent, whether locator index is zero-based, or what happens if the index is invalid or out of range. It discloses no side effects or error behavior.

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 short and to the point, but it spends space re-listing the parameter in a pseudo-formatted block. The core sentence 'Delete a locator.' is concise, while the parameter line is redundant with the schema.

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 operation with no annotations and no output schema, the description is thin. It doesn't clarify what 'locator' refers to, whether deletion is undoable, or how the locator_index is used in the context of the session. More context is needed for an agent to invoke safely.

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 repeats the parameter name and a basic definition ('Index of the locator to delete') that matches the schema's 'Locator Index'. Schema description coverage is 0%, so the description adds minimal value, but it does confirm the parameter's purpose. It lacks details like range, indexing origin, or how to obtain valid indices.

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 'Delete a locator' with a specific verb and resource. It distinguishes from siblings like create_locator and get_locators, though it doesn't explicitly name 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?

No guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing to fetch locator indices via get_locators, or any constraints.

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