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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. Beyond that, the description discloses the response shape (formatted address, country, lat, lon, type, match score), which is genuinely useful since no output schema exists; it only omits guidance on how to read the match score or how multiple results are ordered.

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 compact sentences, front-loaded with the core transform and followed by return fields and a worked example. The trailing example is somewhat redundant with the input schema's examples array, but nothing is padded or buried.

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 three-parameter, read-only lookup with no output schema, the definition covers purpose, return fields, and a concrete invocation, which is enough to call it correctly. The remaining gap is behavioral detail around ambiguous or zero-match queries and result ordering when limit > 1.

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%, with both query and limit documented inline (including the default of 5) plus two examples, so the baseline of 3 applies. The description's example geocode call restates what the schema examples already show rather than adding new semantics such as query formatting rules or ambiguity handling.

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 names a specific verb and resource ('convert an address, place name, or free-text location query into geographic coordinates') and pins the direction of the transform, which implicitly separates it from the sibling reverse_geocode. It also enumerates the returned fields, so an agent knows what it gets back without opening any schema.

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 address-to-coordinate direction tells an agent to pick this over reverse_geocode, but the description never states when to use it versus search_poi, resolve_entity, or search_within. There are no exclusions or prerequisites, so routing is left to inference.

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