read_fandom_page

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

No annotations are provided, so the description carries the full burden. It does add real behavioral context beyond the schema – the content is cached, and source URL plus CC-BY-SA attribution must be preserved – but it never says what happens on a cache miss or whether include_text defaults affect cost/size. Read-only nature is only implied.

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?

Two short sentences with zero waste. The purpose is front-loaded and the routing/attribution guidance follows; every clause earns its place.

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?

An output schema exists, so return values need not be described, and the licensing note is a useful extra. Still missing for an unannotated read tool: cache-miss/error behavior and any hint about the include_text flag's effect on the response.

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 description coverage is 0% for two parameters. The description implies the title parameter exists and must be known, but adds no format guidance (exact title casing, URL vs title), and 'include_text' — the parameter most likely to be misused — is never mentioned or explained.

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?

States a specific verb and resource with scope: 'Read one cached Roblox BedWars Fandom page record.' The word 'one' plus 'cached' distinguishes it from search_fandom_cache and the many other read_* siblings without requiring the schema to be opened.

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?

Explicitly positions it after search_fandom_cache and gives the precondition ('when a page title is known'), which effectively rules out calling it without a title. No explicit when-not statement or alternative for the no-title case, so it falls just short of the top band.

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