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

With no annotations provided, the description carries the full burden of behavioral disclosure. The only disclosed behavior is that the title is discarded after the call, but it does not explain other side effects, permission requirements, or what happens with the unrelated parameters. The description also contradicts the schema by implying a title parameter that does not exist.

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 (two sentences) and easy to read, but it lacks structure and front-loading of the most critical information. It does not explain the input mechanism or output, and the single behavioral note about discarding the title is not prioritized effectively.

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 tool has 9 parameters, none required, no output schema, and no annotations, the description is grossly inadequate. It does not explain how the parameters are used, which one represents the Wikipedia title, what the tool returns, or any preconditions. An agent cannot correctly invoke this tool based on the provided information.

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 description coverage is 100%, so each parameter has its own description, but the main tool description adds no meaning about how these parameters relate to the stated purpose. The parameters (ref, url, city, feed, host, json, path, zone, query) are all unrelated to checking a Wikipedia title, and the description does not clarify which one (if any) is the title. The description fails to add value beyond the schema and actively confuses the mapping.

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 action ('Check whether a Wikipedia title exists'), but it fails to indicate which parameter supplies the title, and none of the 9 schema parameters explicitly represent a title. This ambiguity makes the purpose unclear and misleading for an agent trying to call 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?

The description offers no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or reference sibling tools like 'browser-url-ok' or 'normalize-url', leaving the agent without contextual selection criteria.

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