ha_delete_file

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

The description states the tool deletes files and includes safety restrictions, but lacks details on whether deletion is permanent, confirmation, or error handling. The absence of annotations leaves the agent without warnings about destructive 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?

Two concise sentences: the first states the purpose, the second provides crucial constraints. No unnecessary words, and each sentence adds independent value.

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 with no output schema, the description covers the key aspects: action, path location, and directory restrictions. It could mention permanent deletion, but it is largely complete for the tool's simplicity.

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 describes the path parameter clearly. The description adds value by repeating the relativity to /config/ and noting 'Restricted to safe directories,' which goes beyond the schema. With 100% coverage, the baseline is 3, and this extra context warrants a 4.

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 file from the Home Assistant server,' specifying the action and resource. It also distinguishes from sibling tools like ha_read_file by focusing on deletion and adding path constraints.

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 mentions path is relative to /config/ and restricted to safe directories, giving some context. However, it does not explicitly state when not to use this tool or provide alternatives, such as ha_delete_automation for specific entities.

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