mediawiki_edit_page

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

Expands on annotations (destructiveHint) with warning about overwriting entire content. Discloses authorization needs (bot password) and return value contents (revision ID, diff URL, 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?

Well-structured with labeled sections. Core action stated first. Every sentence is informative and non-redundant. Efficient use of space.

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 complexity (mutation tool with 9 params, destructive, auth required), description covers all critical aspects: purpose, usage conditions, behavioral warnings, parameter hints, return info, and constraints. Output schema exists, so return details are sufficient.

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). Description adds practical hints for parameters like 'summary: required for good practice' and emphasizes that section must be specified to avoid overwrite, but does not cover all 9 params (e.g., rationale, captcha). Still adds meaningful context above baseline.

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?

Clear verb+resource: 'Create new pages or rewrite entire page content.' Distinguishes from siblings with explicit 'NOT FOR' section naming alternatives like mediawiki_find_replace and mediawiki_apply_formatting.

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?

Explicit 'USE WHEN' and 'NOT FOR' sections provide clear context and exclude alternatives. Mentions authentication requirement for anonymous restrictions.

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