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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the title is discarded, but since 'title' is not a parameter, this claim is disconnected from the actual inputs. It does not mention side effects, permission requirements, or return behavior.

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 sentence with no wasted words, but it is severely under-specified and does not front-load actionable information. Conciseness is not a virtue when it omits critical details and misrepresents the tool's functionality.

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 output schema, and no annotations, the description is utterly insufficient. It does not explain how the parameters map to the stated purpose, what the return value is, or any usage context. An agent would be unable to correctly invoke this tool based on the description alone.

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?

Although the schema has 100% description coverage for each parameter, the tool description does not reference any of them. It mentions a 'title' that is absent from the schema, providing no semantic link between the stated purpose and the actual parameters. The description fails to add meaning beyond the schema and even introduces confusion.

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 specific check ('whether a Wikipedia title exists'), but the input schema exposes nine parameters (ref, url, city, feed, host, json, path, zone, query) with no 'title' field. This creates a direct mismatch between the stated purpose and the actual inputs, making the description misleading for an agent trying to invoke the tool.

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 on when to use this tool versus any of the 27 sibling tools. There is no mention of conditions, exclusions, or alternatives, leaving the agent without context for selection.

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