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

The only behavioral note is 'Title discarded after the call,' which is vague because the tool does not identify which parameter is the title. No annotations are provided, so the description carries the full burden. It does not disclose side effects, permissions, or the nature of the check (e.g., network access, caching), leaving significant gaps.

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 short sentences) and has no waste, but it is under-specified. It is not front-loaded with actionable usage information, and the brevity comes at the cost of completeness. Conciseness is appropriate, but structure lacks key details.

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, no output schema, and no annotations, this description is severely inadequate. It does not explain what the tool returns, which parameters are relevant to the stated purpose, or how the tool behaves. An agent cannot correctly invoke this tool based on the given 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?

Schema description coverage is 100%, so the baseline is 3, but the description adds no meaning beyond the schema and actually creates confusion. The schema parameters are generic and unrelated to Wikipedia titles (e.g., 'city' for weather, 'feed' for RSS), and the description does not clarify which parameter to use for the title. The tool fails to compensate for the schema's lack of relevance.

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') and a clear resource, but it does not map to any of the 9 schema parameters. None of the parameters (ref, url, city, feed, host, json, path, zone, query) obviously represent a Wikipedia title, so an agent cannot determine how to supply the title. This ambiguity prevents a fully clear purpose.

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 its many siblings (e.g., browser-url-ok, domain-shape, normalize-url). There is no mention of use cases, exclusions, or alternatives. The one-line description leaves all selection decisions to inference, which is insufficient given the large sibling set.

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