delete_tool

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It states the destructive action ('delete') but omits side effects, permission requirements, reversibility, or error behavior. This is insufficient for safe operation.

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 very concise with two lines, front-loading the action. Every word earns its place, but the extreme brevity sacrifices completeness. It is efficient yet arguably under-specified.

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 one parameter, the description covers the basic action. However, it does not explain return values (despite an output schema existing) or error states. Given the context, it is minimally complete but could benefit from more detail.

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?

With 0% schema description coverage, the description partially compensates by stating 'The UUID of the tool to delete' for the sole parameter 'tool_id'. This adds meaning beyond the schema's type-only definition but remains minimal without format or constraints.

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 tool by ID,' specifying the verb (delete) and resource (tool). While it explicitly distinguishes from sibling delete tools like 'delete_avatar', it lacks additional detail to differentiate further. The purpose is clear but minimally stated.

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 other delete operations or alternatives. There is no mention of prerequisites, conditions, or exclusions. The agent is left without context for appropriate invocation.

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