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

Annotations are absent, so the description carries the full burden. It only notes 'Title discarded after the call,' but gives no insight into return values, side effects, required permissions, or error behavior. The agent cannot predict what happens if the title exists or not, or what the output will be.

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 one short sentence, which is concise, but it lacks structure and helpful elaboration. It is under-specified rather than appropriately sized, since it omits crucial information.

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, and no output schema, the description is grossly incomplete. It fails to explain the purpose of the parameters, the expected input, the return format, or the context for use. An agent would be unable to reliably invoke this tool.

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 schema coverage is 100%, the description adds no connection between the parameters and the purpose. None of the parameter names (ref, url, city, feed, host, json, path, zone, query) obviously map to a 'title,' and the description does not clarify which parameter should carry the Wikipedia title. This creates confusion about how to invoke the tool.

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 and resource: 'Check whether a Wikipedia title exists.' This is a clear verb+resource combination. However, it does not differentiate from sibling tools like browser-url-ok or domain-shape, which might also check existence or validity of similar entities.

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 are no exclusions or mention of related tools. The description lacks any context that would help an agent decide when to select it.

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