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

With no annotations, the description carries the full behavioral burden. It usefully discloses that calls go through OpenAny gateway credentials and that charges/authorization are gateway-determined, but it never states read-only/non-destructive status, rate limits, or result ordering beyond the returned fields.

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?

Two tight sentences: the core behavior and return shape come first, followed by the billing/credential caveat. Nothing is repeated or padded.

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 seven-parameter, fully-described schema with no output schema, the description covers what the tool does, what comes back, and the gateway billing model. It is nearly complete, lacking only read-only confirmation and any note on result ordering.

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 coverage is 100%, so all seven parameters are already documented, including the latitude|longitude format and the gsradius/gslimit bounds. The description adds no parameter-level meaning beyond mentioning coordinates and distances, so the baseline 3 applies.

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 gives a specific verb and resource ("Find English Wikipedia articles near a location") plus the returned fields (titles, coordinates, distances in meters), which clearly separates it from siblings like wikimedia_get_coordinates or wikimedia_get_search. It stops short of naming those alternatives explicitly, so a 4 rather than a 5.

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?

Usage is only implied: the phrasing suggests calling it when you need articles around a coordinate, but there is no explicit when-to-use/when-not-to-use guidance and no pointer to the coordinate or search siblings that could serve overlapping needs.

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