wikijs_delete_tag

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

With no annotations provided, the description adequately discloses that the deletion cascades to all pages and the tag registry, and notes the required environment variables and permissions. It is transparent about the destructive nature of the operation.

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, no filler. The first sentence states purpose and effect, the second provides prerequisites and parameter behavior. Efficient and front-loaded.

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 simple two-parameter tool with no output schema, the description covers action, effect, prerequisites, and conditional parameter. It does not mention error handling (e.g., if tag not found), but that is acceptable for a delete 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 100%, baseline 3. The description adds value by explaining that 'confirm is only checked when WIKI_MUTATION_CONFIRM_TOKEN is set', clarifying the conditional logic beyond the schema's static description.

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 action 'Delete a tag by ID' and the effect 'Removes the tag from all pages and the tag registry'. This distinguishes it from sibling tools like wikijs_delete_comment and wikijs_delete_page.

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 explains prerequisites (WIKI_MUTATIONS_ENABLED=true, manage:system permission) and the conditional behavior of the confirm parameter. However, it does not explicitly state when not to use this tool versus alternatives like update_tag or list_tags.

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