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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and notably openWorldHint=false, so the safety profile is fully covered. The description adds only that the result includes timezone and coordinates; it does not say what happens on an unmatched city, whether multiple matches are returned, or how matching is performed (exact vs fuzzy), which is the meaningful behavior for a lookup tool.

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?

One sentence, front-loaded with the action and its return values, with the usage hint trailing. No filler, no restatement of the title.

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 one-parameter read-only lookup with no output schema, the description usefully names the returned fields and the ambiguity use case. However, it leaves unresolved the exact question it raises — how ambiguous or unmatched names are handled and what the caller should pass to resolve them.

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 single required parameter "query" has 0% schema description coverage, so the schema supplies no meaning at all. The description's phrase "place name" is the only clue about accepted format, and it gives no guidance on disambiguation syntax (e.g., "City, Country") despite explicitly raising ambiguity as the core use case.

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 ("look up a city") and states what the caller gets back (IANA timezone and coordinates), which is more than the title alone conveys. No sibling tool overlaps — the others cover almanac, lunar, and zodiac data — so there is nothing to disambiguate against, but it also doesn't mention its place in that family.

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?

"Useful when a place name may be ambiguous" hints at the triggering situation but is phrased as a benefit rather than an instruction. There are no when-not conditions, no prerequisite statements, and no guidance on how to react if the lookup is itself ambiguous.

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