calculate_sunrise_approx

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

With no annotations, the description must disclose behavior. It states it returns sunrise/sunset hours and daylight duration and implies approximation ('Estimate'), but lacks detail on precision, edge cases (e.g., polar regions), or output format.

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 extremely concise, using only two sentences plus a pointer to related calculators. Every sentence adds value without fluff.

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 simple tool with two parameters and an output schema, the description adequately covers purpose, inputs, outputs, and related tools. It could mention precision or assumptions but is largely sufficient.

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 coverage is 100% with clear parameter descriptions. The description redundantly lists inputs but adds no new semantic meaning beyond what the schema 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 states it estimates sunrise/sunset times for a given latitude and day of year, using the verb 'estimate' and a specific resource. It distinguishes implicitly from exact calculations but does not explicitly differentiate from sibling 'calculate_sunrise_sunset'.

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?

It suggests use for astronomy or outdoor planning and references related calculators via list_bundles, but does not specify when not to use it or compare with alternatives like 'calculate_sunrise_sunset' or 'calculate_sun_exposure'.

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