get-links-here

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds concrete behavioral details: returns up to 500 per call, pagination via continueFrom, and the redirect flag appears only when the referencing page is a redirect. These details augment the 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 a single well-structured paragraph, front-loaded with the main action, then explains type qualifiers, filters, sibling references, limits, and pagination. Every sentence is necessary and informative with no redundancy.

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?

Despite no output schema, the description explains the returned fields (title, page ID, namespace ID, redirect flag) and covers purpose, parameter behavior, limitations, pagination, and sibling advice. It is fully complete for a read-only list tool.

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%, and the description adds context beyond schema by explaining how expandRedirects works (tagging with via redirect), the relationship type behavior, and the redirect flag visibility. This elevates understanding beyond the schema's property descriptions.

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 lists pages that reference a target wiki page, specifying the three relationship types (wikilinks, transclusions, fileusage). It distinguishes from siblings like get-category-members and search-page by explicitly naming them as alternatives.

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?

It explicitly says 'For members of a category, use get-category-members; for full-text content search, use search-page.' It also explains that one relationship per call is allowed and that expandRedirects only applies to wikilinks and fileusage, providing clear guidance on when to use alternatives.

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