wiki_get_page

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

With no annotations, the description fully carries the burden. It discloses that redirects are followed, truncation may occur, waypoint chat codes are relayed verbatim, and skill facts include computed values with game-mode labels.

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 concise at six sentences, front-loading the main purpose. Every sentence adds value, covering return format, data interpretation, and edge cases like redirects and truncation.

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 the simple tool with one parameter and an output schema, the description is complete. It explains the return structure and key behavioral details, leaving no gaps for an agent to misinterpret.

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?

The single parameter 'title' is not described beyond the tool's purpose. While redirects imply some flexibility, there is no explicit detail on expected format, case sensitivity, or whether the title must be exact. Schema coverage is 0%, so the description should compensate more.

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 fetches a Guild Wars 2 wiki page as cleaned plain text, specifying the return fields. It distinguishes from the sibling wiki_search by focusing on retrieving a specific page rather than search results.

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 implies when to use (to fetch a wiki page) and when not to (use wiki_search for searching). It provides detailed guidance on interpreting the returned data, including infoboxes, skill facts, waypoint codes, redirects, and truncation.

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