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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds valuable behavioral context by naming Open-Meteo as the external source, noting the per-call cost, and specifying the GET endpoint. This informs the agent about the external dependency and billing implications beyond the annotations.

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 compact and information-dense, including the mapping, the output categories, the data source, the cost, and the HTTP method in one line. It repeats the title phrase 'Timezone by coordinate,' which is slightly redundant, but overall the structure is efficient and front-loaded with 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?

Given the tool's simplicity, two required parameters, and strong annotations, the description provides adequate context: it lists the return concepts, the external provider, the cost, and the endpoint. There is no output schema, but the description names the important output fields, so an agent has enough information to decide to call it and understand the result.

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 clear examples for lat and lon, so the schema carries the parameter semantics. The description only refers generically to 'Coordinates' and does not add additional meaning about parameter formats, bounds, or coordinate order beyond what the schema already provides.

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 clearly defines the tool's function: converting a coordinate into an IANA timezone, UTC offset, and local time. This is a specific resource-action mapping that distinguishes it from geo-related siblings like reverse_geocode or geocode, which return different data types.

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?

The title 'Timezone by coordinate' implies when to use it, but the description does not explicitly state when it should be preferred over alternatives or mention any exclusions. An agent can infer usage from the coordinate inputs and output fields, but there is no direct routing guidance.

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