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

No annotations are supplied, so the description carries the full burden. It usefully discloses that results can be empty and that calls go through the caller's OpenAny gateway with gateway-determined charges and authorization, which is genuinely helpful context. It does not state read-only behavior or pagination semantics beyond what the schema implies, leaving some gaps for a tool with nine 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?

Three short sentences, with the core purpose front-loaded and the empty-result caveat immediately after. The gateway sentence is boilerplate but does carry billing/authorization information that the agent cannot get elsewhere, so it earns its place, though slightly wordy.

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 simple read tool with full schema coverage and no output schema, the description covers purpose, the empty-result edge case, and auth/billing context. The main missing element is that only English Wikipedia is supported versus other projects, and pagination behavior for colimit over 20 is left to the schema only.

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 every parameter including titles, colimit, continue, and cocontinue is already documented in the schema. The description adds no additional meaning about title formatting or pagination beyond what the schema states, making the baseline 3 appropriate.

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 uses a specific verb and resource ('Retrieve geographic coordinates for an English Wikipedia article'), so an agent immediately knows what it returns. It does not, however, name or distinguish any sibling such as wikimedia_get_nearby (the reverse look-up) or wikimedia_get_wikidata_id, so differentiation is left to the agent.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the alternative coordinate-related tools in the sibling set. The only usage-adjacent statement is that results may be empty for articles without coordinates, which is a caveat rather than routing guidance.

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