mediawiki_get_wiki_info

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

Annotations already declare readOnly and idempotent, so the description adds return value specifics. However, claiming 'PARAMETERS: None' contradicts the schema and misleads about expected inputs, reducing transparency.

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 very concise with three lines plus a structured 'USE WHEN' section. No unnecessary verbiage; information is front-loaded.

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 low complexity (no required params, output schema present), the description covers purpose, usage, and return info. It misses mentioning the optional rationale parameter's purpose, but output schema likely covers details.

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% but the description says 'PARAMETERS: None', which is incorrect given the rationale parameter. This diminishes rather than adds meaning beyond the 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?

The description clearly states it retrieves wiki information and gives specific use cases (wiki statistics, version). However, it inaccurately says 'PARAMETERS: None' while the schema includes an optional rationale parameter, slightly clouding the purpose.

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 'USE WHEN' section explicitly lists user queries that trigger this tool, providing clear guidance on when to use it among many sibling tools.

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