mediawiki_manage_categories

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

Annotations already provide destructiveHint=true and openWorldHint=true. The description adds behavioral context by noting that changes are made without editing full content, offering a preview option, and detailing return information including revision ID, diff URL, and undo instructions. It does not contradict annotations.

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?

The description is well-structured with clear headings and is appropriately concise. Each section (USE WHEN, NOT FOR, PARAMETERS, RETURNS) adds value without redundancy. It front-loads the core purpose and then organizes additional details logically.

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 the tool's complexity (5 parameters, all described in schema, output schema exists, annotations present), the description is fully complete. It covers usage scenarios, parameter details, and return information, leaving no obvious gaps for an AI agent to invoke the tool correctly.

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. The description adds meaning beyond the schema by explaining the 'add' and 'remove' parameters require category names without the 'Category:' prefix, and gives examples of when to use each parameter. This extra context enhances understanding.

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 tool's purpose: 'Add or remove categories from a page without editing the full content.' It specifies the verb ('add or remove') and resource ('categories on a page'), and explicitly distinguishes from sibling tools like mediawiki_list_categories and mediawiki_get_category_members.

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 includes explicit usage guidance with 'USE WHEN' and 'NOT FOR' sections, providing clear directives for when to invoke this tool and when to use alternatives. It names specific sibling tools for alternative cases.

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