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

Beyond the read-only annotations, it discloses source (Wikidata CC0), pricing, the free quota, that failed calls are free, and that repeated calls are charged. It also reiterates that the tool changes nothing, which is consistent with the readOnlyHint annotation.

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 front-loaded with purpose and return fields, then follows with usage, example, pricing, and safety notes. It is generally efficient, though the read-only restatement is partly redundant with annotations and the pricing sentence is dense.

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 two-parameter geocoding tool with no output schema, the description is complete enough: it names the source, lists returned fields, explains result ordering, gives an example, and covers billing and read-only behavior.

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 both the name and count parameters are already documented in the schema. The description adds an example and the fact that results are best match first, but it does not add syntax or matching nuance beyond that.

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 verb and resource: find places by name in Wikidata and return their coordinates and related place metadata. It clearly scopes this as forward geocoding by name, which distinguishes it from siblings such as geocode_reverse and geo_distance.

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?

It gives clear usage context: use before weather, sun, or distance lookups, and use it to disambiguate places with the same name. It does not explicitly route users to geocode_reverse for coordinate-to-place lookups, but the by-name scope makes the distinction reasonably clear.

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