Quality of Time

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful non-schema facts — the POST endpoint and a 10-credit Tier 1 cost — which the agent would otherwise not know. It still says nothing about what the computation returns or how deterministic/interpretive the result is.

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 pure-purpose line is front-loaded and the bracketed metadata is scannable and waste-free. It is short to a fault, but nothing written is filler.

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 13-parameter Hellenistic computation tool, the description says almost nothing about which optional parameters actually change the answer or what the result represents. An output schema exists so return values need not be explained, but the gap on optional-parameter relevance and on sibling disambiguation leaves the definition incomplete.

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?

With 13 parameters and only 23% schema description coverage, the description must compensate, but it merely restates the four required fields already in the schema's `required` array. The eight optional parameters — ayanamsa, zodiacType, houseSystem (25-value enum), timezone, timezoneOffset, cosmogram — get no mention, so an agent has no cue that they matter.

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?

"Synchronistic quality of a moment" names a concept but no verb and no resource; an agent cannot tell what is actually computed (planetary sect quality? sect light condition? a score?). The group tag 'Hellenistic: Greenbaum tradition' narrows the domain, but the description never contrasts this with the many other timing tools (vedic_muhurta_*, chinese_tong_shu_select, horary_*).

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?

No statement of when to choose this over the dozens of sibling timing/electional tools, and no prerequisites or constraints beyond the required-parameter list. The bracketed metadata gives endpoint and cost, which is operational context, not usage guidance.

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