mediawiki_move_page

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

Annotations already set destructiveHint: true and openWorldHint: true. The description adds context by noting that the operation creates a redirect by default, requires move permissions, and includes a warning. It also describes the return value (revision ID, diff URL, undo instructions). No contradictions.

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 sections: USE WHEN, NOT FOR, PARAMETERS, RETURNS, WARNING. Every sentence serves a purpose, no 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 the tool's complexity (6 parameters, 2 required) and the presence of annotations and an output schema, the description covers purpose, usage guidelines, parameter explanations, return values, and warnings. It is fully complete.

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 description coverage is 100%, so baseline is 3. The description rephrases each parameter clearly (e.g., 'from: Current page title') and adds default values for booleans (default false/true), which adds value beyond the schema alone.

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 'Move (rename) a wiki page. Creates a redirect from the old title.' This specific verb+resource pair distinguishes it from sibling tools like mediawiki_edit_page and mediawiki_find_replace, both mentioned in the 'NOT FOR' section.

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 a 'USE WHEN' section listing common user phrases and a 'NOT FOR' section explicitly excluding editing tasks, with alternatives provided (mediawiki_edit_page, mediawiki_find_replace). This gives clear guidance on when to use the tool versus siblings.

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