delete_bot

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

No annotations provided, so the description must disclose behavioral traits. It only says 'Delete', which is minimal. The parameters hint at hard vs soft delete and recursive behavior, but the description does not explain these aspects or the consequences of deletion.

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 a single sentence, achieving conciseness, but it lacks necessary detail. It is front-loaded with the action, but the brevity undermines its usefulness. Every sentence should earn its place; here the one sentence does the bare minimum.

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?

Given no annotations, no output schema, and three parameters with zero documentation, the description is severely incomplete. It fails to provide essential context for an AI agent to correctly invoke the tool and understand its effects.

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 description coverage is 0%, and the description adds no explanation for the three parameters (bot_id, hard_delete, recursive). An agent cannot infer their meaning or defaults from the tool description alone.

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 bot from OpenMetadata', using a specific verb and resource. It differentiates from sibling delete_* tools that target other entity types (chart, classification, etc.). However, it is brief and does not elaborate on the deletion semantics.

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 on when to use this tool versus alternatives like get_bot or update_bot. No prerequisites or context provided (e.g., need bot_id from list_bots). The tool's role in a workflow is not explained.

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