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

No annotations are provided, so the description carries the full behavioral burden. It mentions 'no key' and 'REST summary,' which hints at a network read, but it does not disclose rate limits, error behavior, or what happens with empty or invalid input. This is minimal coverage for a tool with no annotation safety hints.

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 'Wikipedia Summary:' and 'Wikipedia REST summary:' are redundant, and the remaining text is so compressed that it sacrifices necessary meaning. It is under-specified rather than efficiently concise.

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?

For a tool with one optional parameter and an output schema, the description still fails to explain the parameter or how to construct a valid query. It also provides no context for choosing among several wiki-related sibling tools, leaving the agent to guess at the intended usage.

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 sole parameter q has 0% schema description coverage and is not explained in the tool description at all. The description's mention of extract, type, and coords does not clarify whether q is a page title, query string, or something else, leaving a critical gap.

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 identifies the resource as a Wikipedia REST summary and names key fields (extract, type, coords), so an agent can infer the tool's function. It is clear enough to be usable, though it lacks a direct verb and does not distinguish itself from the sibling wikisummary 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?

There is no guidance about when to use this tool versus alternatives like wikisummary, nearbywiki, or trendingwiki. The description gives no conditions, exclusions, or context that would help an agent decide between sibling tools.

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