Horary Planetary Hours

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds context about the return value (planetary hour ruler and match check) and provides an example request, going 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 short and to the point, with two sentences plus a group/cost note and example. It is front-loaded with the key action, though the example could be better integrated into parameter descriptions.

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 lack of output schema and parameter descriptions, the tool description leaves gaps in understanding the output structure and the exact matching logic. The annotations partially fill safety context, but completeness is adequate for a simple tool.

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 0%, and the description does not explain individual parameters. Only an example request body is provided, which gives format clues but lacks semantic meaning for each parameter (e.g., latitude, longitude, timezoneOffset).

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 the tool returns the planetary hour ruler and checks if it matches the ASC ruler, specifically for a horary question. This distinguishes it from siblings like 'planetary_hours' and other horary tools.

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 description implies use for horary questions but does not explicitly guide when to use this tool over alternatives like 'planetary_hours' or 'horary'. No exclusion or alternative mentions.

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