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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds real value beyond that by disclosing the downstream effect — existing plans referencing the piece can no longer be produced — which is exactly the kind of consequence an agent needs before invoking a delete.

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 short sentences, zero filler, with the object definition front-loaded and the destructive consequence second. Every clause earns its place.

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 one-parameter destructive delete with full annotation coverage and no output schema, the description supplies the essential missing piece: what breaks after deletion and how to recover. Minor gaps remain (whether deletion is soft/hard, what happens to plans already in flight), but nothing blocks correct invocation.

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?

Single parameter with 100% schema description coverage ("The kit piece id"), so the schema carries the semantics. The description adds nothing about the id's form or where to obtain it (presumably list_kit), which is the baseline expectation when coverage is complete.

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?

States a specific verb ("Remove") plus the resource, and crucially defines what a kit piece actually is ("outfit, place or prop"), which the name alone does not convey. It doesn't explicitly distinguish itself from nearby delete tools like delete_look or delete_video, so sibling differentiation is only partial.

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 consequence clause ("A plan that used it can't be made any more: plan again") gives a workflow signal about when this is appropriate and what to do afterwards. However, no alternatives are named and no explicit when-not-to-use condition is given, leaving tool selection largely implied.

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