Reverse Bazi To Solar Times

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

Annotations already indicate readOnly, destructive, idempotent, and open-world hints. The description adds specific behavioral context: the lookup uses 'clock-time pillars without location-based true solar correction,' which is critical for understanding result accuracy. No contradictions with 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 extremely concise: two sentences that front-load the purpose and add one essential behavioral note. Every sentence is necessary and no wasted words.

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 5 parameters, 100% schema coverage, and no output schema, the description provides the core use case and a key behavioral detail. It could mention the output format (list of datetimes) but is otherwise complete.

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%, so the baseline is 3. The tool description does not add meaning beyond the schema for individual parameters, but it contextualizes the overall lookup behavior. No contradiction.

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's purpose: 'Find possible Gregorian datetimes that produce a given four-pillar Bazi string.' It uses a specific verb ('find') and resource ('Gregorian datetimes'), differentiates from sibling tools by mentioning the lookup is without true solar correction, and is useful when a user only has a Bazi chart.

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 when to use the tool (when a user has a Bazi string and wants possible datetimes) and notes the lack of solar correction, hinting that for solar-adjusted times another tool (calculate_true_solar_time) may be needed. However, it does not explicitly list when not to use it or name alternatives.

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