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

With no annotations, the description carries the burden well: it discloses the 50% blueprint-cost refund, the non-obvious rule that refunds never reset daily spending, and the UUID requestId requirement (an idempotency signal). It omits that the destruction is irreversible and what errors occur if the invention isn't active or isn't owned.

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?

Three tight clauses, front-loaded with verb and resource, then effect, then constraints. No filler or restatement of the tool name.

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, no-annotation, no-output-schema mutation, the definition covers refund economics and the idempotency key but leaves out irreversibility, failure modes, and any indication of what is returned. Adequate but with clear gaps for a destructive operation.

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 coverage is 0%, so the description must carry parameter meaning; it does partially by explaining that inventionId targets an owned active invention and that requestId must be a UUID. It never explains what requestId is for (idempotency/deduplication), leaving the agent to guess its semantic role.

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 (dismantle) and resource (an active invention you own) plus the economic effect, which clearly separates it from build_invention, gift_invention, and invention_inventory. It stops short of naming a sibling alternative, but the action is unambiguous.

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 ownership and 'active' preconditions imply when the tool applies, but the description never states when NOT to use it (e.g., use gift_invention to transfer instead of destroying) or what happens for inactive/foreign inventions. Usage is inferable rather than guided.

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