Delete a tag, category or tool

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

Beyond annotations (destructiveHint: true), it explains that recipes are kept but lose assignment, and details the confirmation mechanism. No annotation contradiction; description adds significant behavioral context.

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 sentences, all content earns its place: first sentence states what it does and side effect, second explains the confirmation flow. No fluff or redundancy.

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 output schema and complete schema coverage, the description covers all needed behavioral aspects: action, side effects, confirmation process. No gaps remain for safe usage.

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 100%, so baseline is 3. Description adds value by explaining confirm_token workflow (not in schema description) and provides context for kind enum values ('free-form labels', 'primary classification'). The description could briefly clarify id format since it's a UUID.

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 specific verb ('Deletes') and resource ('tag, category or tool'), with clear scope. It distinguishes from siblings by explaining deletion behavior vs. recipe preservation, which isn't covered by other tools.

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?

Explicitly describes the two-step process: first call gets a token, second call uses it for confirmation. No alternative tool is needed as deletion is unique; guidelines are complete and actionable.

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