delete_command

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

The description only says 'Delete a custom command,' implying a destructive action but providing no details about irreversibility, required permissions, side effects on related data, or whether deletion is permanent. With no annotations, the description carries the full burden and fails to disclose important behavioral traits.

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?

While the description is very short (one sentence), it is under-specified rather than concise. It omits critical information that would fit in a few more sentences, making it ineffective despite its brevity.

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 delete operation with 2 parameters and no output schema, the description should explain the `dry_run` parameter and the expected outcome. It fails to provide enough context for correct invocation, leaving the agent uninformed.

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 schema has 0% description coverage, and the description does not explain any parameters. The `command_id` and `dry_run` fields are left completely unexplained, forcing the agent to guess their meaning and usage.

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 'custom command,' which distinguishes it from siblings like add_command, list_commands, and update_command. However, it is essentially a tautology of the tool name and adds little extra context.

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 versus alternatives, such as when to use update_command or toggle_default_command. There are no prerequisites, warnings, or conditions mentioned.

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