delete_bots

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

With no annotations provided, the description carries full burden. It discloses that deletion is reversible with a 10-day backup and requires a specific key. However, it does not mention any side effects (e.g., impact on dependent resources like commands or storage) or what happens if the key is missing.

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?

Single sentence conveys all essential information without superfluous words. It is front-loaded with the action and key constraint.

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 deletion tool with one parameter and no output schema, the description covers the core behavior (soft-delete, recovery window, key requirement). However, it lacks details on the response format or any side effects on associated resources, leaving some ambiguity.

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% with a clear description for the only parameter (ids). The tool description adds minimal extra meaning beyond stating it can take a single ID or array. The parameter is simple, so this is adequate.

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 (soft-delete) and the resource (one or more bots), and distinguishes it from permanent deletion or recovery by mentioning the 10-day backup window. Sibling tools like purge_deleted_bot and recover_deleted_bot are clearly different.

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?

The description explicitly requires an sk_* key, which is a necessary prerequisite. It implies the tool is for soft-deletion with recovery options, but does not explicitly state when not to use it or name alternatives like purge_deleted_bot for permanent deletion.

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