calculate_synastry

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

Discloses that it compares positions and calculates aspects, but lacks details on output format, calculation methodology, or any side effects. With no annotations, the description carries the burden but is insufficiently detailed.

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?

Two concise sentences with no fluff. Every word adds value: clear verb, resource, and what the calculation entails. Well-structured.

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 is provided, yet the description does not detail the return values. For a tool with 6 required parameters and no annotations, the description is insufficiently complete; it should hint at the output structure or any important behavioral details.

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 descriptions for all 6 parameters. The description adds no additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 verb 'calculate' and resource 'synastry chart', and explains it compares planetary positions and aspects for relationship compatibility. It uniquely distinguishes from sibling tools like calculate_planetary_positions (single person).

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?

Implies usage for relationship compatibility but does not explicitly state when to use this tool versus alternatives like calculate_transits or calculate_solar_revolution. No exclusions or prerequisites are mentioned.

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