clear_and_replace_commands

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

With no annotations provided, the description carries full burden. It discloses the destructive behavior ('removes all existing commands first'), which is crucial for a mutation operation. However, it lacks details on permissions needed, whether changes are reversible, error conditions, or response format. The description adds value but doesn't fully compensate for missing 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?

Two concise sentences with zero waste. The first sentence states the purpose, and the second clarifies the behavioral implication. Every word earns its place, and information is front-loaded appropriately.

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 destructive mutation tool with no annotations and no output schema, the description is adequate but has clear gaps. It covers the core action and destructive nature, but lacks details on permissions, reversibility, error handling, and return values. Given the complexity, it should do more to compensate for missing structured data.

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 100%, so the schema already documents both parameters ('test_id' and 'commands'). The description adds marginal context by implying 'commands' should be a complete new set, but doesn't provide syntax or format details beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('Replace ALL commands'), target resource ('in a test'), and scope ('with a new set'). It distinguishes from siblings like 'add_commands' (which adds without removal) and 'fix_commands' (which implies modification rather than full replacement).

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 usage context by stating 'removes all existing commands first,' suggesting this tool should be used when a complete replacement is needed rather than incremental changes. However, it doesn't explicitly name when-not-to-use scenarios or alternative tools like 'add_commands' for partial updates.

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