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

With no annotations provided, the description carries the full burden. It only says 'Title discarded after the call,' which hints at data handling but does not clarify side effects, read-only behavior, or what the caller should expect beyond a yes/no existence result.

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 short and front-loaded, with no filler or redundant content. It earns its place but could have better structured the relationship between the stated purpose and the actual parameters.

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?

With 9 parameters, no required fields, no output schema, and a mismatched parameter list, the description is far from complete. An agent cannot determine how to invoke this tool or interpret its result.

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 schema properties (ref, url, city, feed, host, json, path, zone, query) are unrelated to checking a Wikipedia title, and the description fails to explain which parameter represents the title. The existing property descriptions are present but misleading for this tool's purpose.

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 states a clear verb+resource ('check whether a Wikipedia title exists'), but the schema contains no 'title' parameter, so the actual intent is ambiguous. It does distinguish from sibling tools by naming Wikipedia titles, but the mismatch weakens the clarity.

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?

No guidance is given about when to use this tool versus sibling tools like browser-url-ok, file-path-ok, or domain-shape. The description only states what it checks, not when it should be preferred or avoided.

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