delete_my_commands

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

The description simply says 'Delete', which aligns with the destructiveHint annotation but adds no additional behavioral context. It does not explain default scope/language behavior, the effect on existing commands, or any side effects. With annotations already covering destructiveness, the description contributes little beyond the annotations.

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 concise sentence that is front-loaded with the action and target. It is efficient, though it could benefit from one additional sentence about parameter defaults or usage context without becoming verbose.

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 only 2 parameters, no output schema, and sparse annotations, the description is too thin. It does not cover prerequisite conditions (e.g., commands must have been set), what happens if no parameters are provided, or the meaning of 'scope' variations. This is inadequate for safe invocation of a destructive operation.

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 clarify the parameters. It only mentions 'scope and language' without explaining valid values, defaults, or semantics of the empty 'scope' schema property. This is insufficient for an agent to set parameters correctly.

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 uses a specific verb ('Delete') and resource ('the bot's command list') and includes qualifiers ('for a given scope and language'). It clearly distinguishes from sibling tools like get_my_commands and set_my_commands, which serve different purposes.

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 implies when to use the tool (to remove commands) but provides no explicit comparison to alternatives. It does not state exclusions or mention that set_my_commands is the opposite operation, so guidance is limited to what can be inferred from the name and siblings.

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