sidecar_reset

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

The description clearly indicates destructiveness ('Wipe') and lists what is reset, but without annotations it lacks warnings about irreversibility or potential side effects. Adequate but minimal.

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?

One sentence that efficiently communicates purpose and scope with no wasted words.

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 no annotations, the description covers the tool's destructive scope fully. It lacks return value details, but output schema may compensate. Complete enough for a reset tool.

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?

No parameters exist, so the description adds no parameter info. Baseline for 0 parameters is 4; the description still adds value by explaining what is wiped.

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 strong verb 'Wipe' and specifies the exact resources affected (kv_store, leases, workflows, etc.). It clearly distinguishes from sibling tools which handle individual operations.

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 explicit guidance on when to use this tool versus performing individual deletions via state_delete, lease_release, etc. The description implies it's for a full reset but doesn't state prerequisites or alternatives.

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