timezone_get

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

No annotations provided; description does not disclose behavioral traits such as rate limits, authentication, error handling, or behavior for invalid coordinates. Does not mention impact of optional 'timestamp' on DST.

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?

Extremely brief single sentence, but fails to provide necessary details. Not front-loaded with actionable info; does not earn its place given the complexity of the tool.

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?

No output schema and no annotations; description is insufficient for an agent to understand return format or behavior. For a tool with 4 parameters (2 optional), more context is essential.

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 fully describes all 4 parameters with descriptions. Description adds no extra meaning beyond the schema; for example, it does not explain how 'language' affects output or that 'timestamp' adjusts for DST.

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?

Description clearly states the tool retrieves timezone information for a location, distinguishing it from sibling tools like elevation_get or geocode. However, it lacks specificity about what information is returned (e.g., offset, DST).

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?

No guidance on when to use this tool vs alternatives like geocode_reverse or places_details. No mention of prerequisites, required input constraints, or context for the optional parameters.

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