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

With no annotations, the description carries the full burden of explaining side effects and state changes. It only says a title is discarded after the call, but no title input exists in the schema, making that statement effectively meaningless. It does not disclose how the tool behaves with the provided ref, url, city, feed, host, json, path, zone, or query parameters.

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, but it is short at the expense of usability. It front-loads the wrong concept ('title') and includes a discard note that does not map to the actual input schema, so every sentence either misleads or fails to help the agent.

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 has nine optional parameters, no output schema, and no annotation safety context, yet the description explains none of these. It is impossible for an agent to infer which parameter to use, what the result means, or how calling this tool differs from calling adjacent tools.

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 description adds no semantic value to the parameters; it never associates the 'Wikipedia title' concept with any of the nine schema properties. Although the schema has 100% description coverage, the schema descriptions are generic one-liners such as 'discarded after the shape check' and do not support the stated purpose of looking up a Wikipedia title.

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 says 'Check whether a Wikipedia title exists,' which names a clear verb and resource, but there is no parameter for a Wikipedia title in the input schema. The phrase 'Title discarded after the call' is misleading because no parameter is named 'title' and all nine properties are unrelated to Wikipedia titles.

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 for when to use this tool versus its many siblings, such as browser-url-ok, file-path-ok, validate-json, or search-query-len. The description does not explain which of the nine unrelated parameters should be populated or in what combination.

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