mediawiki_get_backlinks

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds that it returns a list of pages and notes parameter defaults (limit 50, include_redirects false), providing useful behavioral context beyond 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?

The description is well-structured into clear sections: one-line purpose, USE WHEN/NOT FOR, PARAMETERS, RETURNS. It is concise with no wasted words, front-loaded with the core 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 a simple tool with 5 parameters (including rationale), output schema existence, and clear return description ('List of pages'), the description is complete. It also distinguishes from a relevant sibling, covering all necessary context for an agent.

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 adds default values for limit (50) and include_redirects (false) not fully covered in schema, and clarifies optionality of parameters, adding value 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 starts with 'Get pages that link TO a specific page ("What links here")' which is a clear verb+resource. It distinguishes from sibling mediawiki_get_external_links by explicitly stating it is not for outgoing external links.

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 provides 'USE WHEN' examples (e.g., 'what links to X') and 'NOT FOR' excluding outgoing links with an explicit alternative tool. This gives clear guidance for when to select this tool.

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