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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and open-world profile. The description adds that results include the matched center and IANA timezone, but nothing about rate limits, auth, or edge behavior. With annotations carrying the safety profile, this is adequate but adds limited behavioral depth.

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 tightly written sentences: the capability first, the disambiguation second. No filler, and the routing guidance is front-loaded after the core purpose.

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?

An output schema exists, so return values needn't be spelled out, and annotations cover the safety profile. The description covers purpose, alternatives, and coordinate input adequately; only minor behavioral depth (e.g., locale effect on returned address) is absent.

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% – latitude, longitude, lang, and country are all documented with types and defaults in the schema. The description adds no parameter syntax or constraint beyond what the schema already provides, 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?

States a specific verb (fetch) and resource (Apple Maps address records) plus the mechanism (reverse geocoding from a coordinate). It explicitly names two sibling tools (geocoding_reverse, apple_maps_search), so an agent can distinguish it from nearby Apple Maps and geocoding tools without opening a 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?

Gives explicit routing: use geocoding_reverse for the general reverse-geocoder, or apple_maps_search for nearby places. The when-to-use-this-vs-alternatives condition is stated, not implied.

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