Delete a specific command from history

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

The description claims a destructive action ('Delete'), but the annotation destructiveHint is false, creating a direct contradiction. Additionally, it does not disclose any side effects, permanence, or permissions needed.

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 short but repeats itself: 'Delete a specific command from history' and 'Deletes a specific command from the history of a host' say nearly the same thing. It could be one concise sentence.

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?

With two undocumented parameters, no output schema, and no behavioral notes, the description is inadequate for a deletion operation that could have irreversible 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?

The schema has zero description coverage and the description does not explain the hostId or command parameters, leaving the agent without guidance on required fields, format, or matching semantics.

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 (delete) and the resource (a specific command from history), and adds the scope 'of a host'. It is distinct from sibling get/list tools, though the second sentence is redundant.

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?

There is no guidance on when to use this tool versus alternatives, no conditions, and no mention of required parameters. It only states the action without context or exclusions.

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