delete_entity

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

With no annotations, the description must disclose behavioral traits. 'Permanently delete' only implies destructiveness, but it omits details like whether deletion is reversible, cascading effects, required permissions, or rate limits. The description fails to provide sufficient transparency for a destructive 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 extremely concise (4 words), but this brevity sacrifices structure and explanatory value. It is not verbose but lacks any formatting or hierarchy, making it barely structured.

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?

Despite having an output schema, the description does not mention what the tool returns or any side effects. For a permanently destructive action, more context (e.g., on error handling, success response, or necessary permissions) would be expected. The description is incomplete for the tool's complexity.

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?

Schema coverage is 100% for both parameters (api_key, entity_id). The description adds no additional meaning beyond the schema, which already describes the parameters. Baseline 3 is appropriate as the schema carries the load, and the description does not enhance parameter understanding.

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 action 'permanently delete' and the resource 'entity', making the tool's purpose unambiguous. However, it does not clarify what constitutes an 'entity' in this context, which could lead to confusion among sibling tools dealing with specific entity types like monitors or datasets.

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 tools (e.g., delete_monitor, delete_job). The description lacks prerequisites, conditions, or any instruction on which entity deletion scenarios are appropriate for this tool.

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