Delete Autocomplete File

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

Beyond the destructiveHint annotation, the description reinforces the destructive action with 'DESTRUCTIVE' and specifies the operation is on a 'local' file, offering additional context about scope. However, it does not detail potential side effects or confirmation requirements.

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 concise and well-structured, including the HTTP method, endpoint, and a clear warning. It conveys the essential information without unnecessary verbosity.

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 delete operation with a single parameter, the description is complete. It explains the action, the target, and the destructive nature, which is sufficient for an agent to use the tool correctly without needing additional details.

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 already provides a description for the 'name' parameter ('Autocomplete file name to delete'). The tool description does not add further meaning or constraints beyond this, so the baseline score for full schema coverage 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 clearly states the tool deletes a local autocomplete/tag-list file, specifying the exact HTTP method and endpoint. It is distinct from siblings like autocomplete_download and autocomplete_content.

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 does not explicitly indicate when to use this tool versus alternatives. It provides no context about when deletion is appropriate or what distinguishes it from other autocomplete-related tools, aside from the obvious destructive nature.

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