Group Synastry

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that it returns pairwise matrices, which is useful, but does not disclose other traits like cost (though cost is in the group note) or potential limitations. With annotations covering safety, the description provides moderate added value.

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 concise (one sentence plus a group tag and example), front-loads key information, and avoids unnecessary details. Every element serves a purpose.

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 complexity of group synastry and the lack of output schema, the description provides the essential output format (pairwise matrices). It is reasonably complete for an AI agent familiar with astrology, though it could detail orbs or aspect types.

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?

The description includes an example request body, which aids understanding of the parameter structure. However, it does not explain each parameter's meaning or constraints beyond what is in the schema. With 0% schema description coverage, the description adds marginal value.

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 calculates synastry aspects among 2-8 charts and returns pairwise cross-chart aspect matrices. However, it does not differentiate from sibling tools like 'synastry' or 'synastry_aspect_grid', which may lead to confusion about when to use this specific tool.

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 usage for group synastry but does not explicitly state when to use this tool versus alternatives like the regular 'synastry' tool. There is no guidance on when not to use it or alternative tools.

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