mediawiki_move_page

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

Annotations indicate destructiveHint=true and openWorldHint=true. The description adds context: 'Requires move permissions', 'Creates a redirect from the old title by default', and mentions return values including undo instructions. No contradiction with 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?

Description is well-structured with clear headings (USE WHEN, NOT FOR, PARAMETERS, RETURNS, WARNING). It is concise and front-loaded; every sentence serves a purpose.

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 many siblings, the description effectively differentiates. It covers purpose, usage, parameters (with minor omission), return values, and warnings. Output schema may cover returns, but the description's mention of undo instructions adds value.

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 lists parameters with defaults (e.g., no_redirect default false) not in schema, adding value. However, it omits the required 'rationale' parameter from its list, which is a gap.

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 action: 'Move (rename) a wiki page. Creates a redirect from the old title.' It uses a specific verb and resource, and distinguishes itself from siblings like mediawiki_edit_page by noting it's not for editing content.

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 explicitly provides 'USE WHEN' and 'NOT FOR' sections, giving clear usage context. It names alternative tools (mediawiki_edit_page, mediawiki_find_replace) to guide correct selection.

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