mediawiki_get_images

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

Annotations already declare readOnly=true, idempotent=true, openWorldHint=true. Description adds valuable context about return types (titles, URLs, dimensions, file sizes), fully aligning 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?

Structured into USE WHEN, PARAMETERS, and RETURNS sections. Every sentence adds value. Concise and well-organized for agent consumption.

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?

With output schema present and schema coverage 100%, description adds return type details. Sufficient for a straightforward read-only tool with 3 parameters. No gaps identified.

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 covers all parameters with descriptions (100% coverage). Description restates 'title: Page name (required)' and 'limit: Max images (default 50)', but the schema already includes defaults and constraints. No additional semantic value beyond schema.

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?

Description clearly states 'Get all images and files used on a wiki page.' with specific verb and resource. Usage cues further clarify scope. Distinguishes from sibling tools that handle pages, revisions, categories, etc.

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' section provides clear context for agent to select tool. No explicit 'when not to use' or alternatives listed, but the description is sufficient given sibling diversity.

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