divine_get_matching_horoscope_chart

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds that it returns both P1 and P2 charts, which is useful, but it does not disclose additional behavior such as error handling, chart format details, or any operational constraints.

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 and front-loaded with the core purpose, followed by the return detail. There is minor redundancy between 'Generate horoscope charts' and 'Returns charts for both P1 and P2,' but the overall length is appropriate and every sentence contributes useful information.

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 tool with 26 parameters and a rich schema plus an output schema, the description adequately covers the essential outcome: generating and returning both matchmaking charts. It does not need to repeat parameter details already present in the schema, though it could briefly mention that full birth details for both persons are required.

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 schema already documents every parameter. The description adds only minimal semantic value by referring to the 'specified divisional chart type,' which aligns with chart_id; this is the expected baseline when the schema carries the parameter documentation burden.

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 states a specific verb ('Generate'), a specific resource ('horoscope charts for both persons in matchmaking'), and clarifies that both P1 and P2 charts are returned for a specified divisional chart type. This clearly distinguishes it from single-person chart tools and other matching 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 phrase 'in matchmaking' and 'enabling visual comparison' imply the intended use case, so an agent can infer when this tool is appropriate. However, it does not explicitly mention when not to use it or name alternatives such as divine_get_horoscope_chart or other matching-specific tools.

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