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

The description says 'Title discarded after the call', which hints at no data retention, but it is unclear because there is no 'title' field in the schema. There is no mention of side effects, errors, or other behavioral details. No annotations are provided to supplement.

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 (one sentence), but the structure is confusing due to the disconnect between the declared purpose and the schema. There is no additional structure to help the agent understand the tool's operation.

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?

The tool lacks a parameter for the title, which is essential for its stated purpose. There is also no information about the return value or how to interpret the result. The tool is incomplete for its intended use.

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?

All 9 parameters (ref, url, city, feed, host, json, path, zone, query) have descriptions that are irrelevant to checking a Wikipedia title. The descriptions appear copied from other tools and do not clarify how to specify the title or how these parameters relate to the described 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 purpose ('Check whether a Wikipedia title exists'), but the input schema contains no 'title' parameter, making it ambiguous how to actually invoke the tool. The purpose is undermined by the mismatch between description and schema.

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 provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or comparison with sibling tools such as 'browser-url-ok' or 'fetch-status'.

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