delete_action

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

The description implies a destructive action but does not explicitly state that the deletion is irreversible, require permissions, or affect associated data. With no annotations provided, the description carries the full burden of behavioral disclosure, yet it adds no traits beyond the operation name.

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 at 5 words, front-loaded with the key action and resource. Every word serves a purpose with no unnecessary detail.

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 tool, the description lacks completeness. It does not mention the permanent nature of the deletion, required permissions, or any side effects. Given the lack of annotations and output schema, more context would be beneficial for safe usage.

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 tool description does not mention any parameters, and the schema description coverage is 0% (per context), meaning the description should compensate. Although the schema includes a description for 'id', the tool description adds no meaning beyond the schema, failing to enhance understanding of the input.

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 verb 'Delete' and the resource 'action from Metabase', making the purpose immediately understandable. It distinguishes itself from sibling tools like create_action and update_action by specifying the delete operation.

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 over alternatives, such as delete_action_public_link or other delete tools. There are no prerequisites, context, or exclusions mentioned, leaving the agent without decision-making support.

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