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

With no annotations, the description carries the full burden, and 'permanently' is the one useful disclosure — it flags irreversibility. It says nothing about what collateral data is destroyed (conversations, knowledge sources, embed code, widget config), whether elevated permissions or confirmation are required, or whether the operation can fail on an in-use bot.

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?

One short sentence, front-loaded with the destructive verb, no filler. Its brevity is a virtue on this dimension, though the size reflects under-specification rather than disciplined editing.

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 permanent, irreversible mutation with no annotations, no output schema, and undocumented parameters, the description should cover blast radius and failure modes. None of that is present, so an agent cannot predict consequences of calling it.

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%, so the description must explain bot_id, and it does not — no format, no source of the ID, no indication of what happens with an unknown or already-deleted ID. The single parameter is only guessable from its name.

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?

Specific verb (delete) plus resource (chatbot), and 'permanently' adds real scope information beyond the name. It does not distinguish itself from adjacent destructive siblings such as purge_bot_knowledge or delete_knowledge_source, so an agent must infer that this removes the bot object itself.

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 statement of when to use this versus update_chatbot, purge_bot_knowledge, or delete_knowledge_source, and no preconditions (ownership, active-conversation state) before invoking. The agent is left to infer that permanent deletion is the last-resort path.

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