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

Annotations already declare this read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds nothing behavioral: no note on determinism, whether the same moment always yields the same reading, what the output contains, or what 'quality of time' actually returns. For a computation tool of this type that gap is significant.

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 text is short but wastes its few tokens on cost tier and group taxonomy while omitting the actual purpose. It is front-loaded with a vague phrase and then spends its budget on metadata rather than task-relevant content.

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?

With an output schema present, return values need not be explained, but the description should still convey what this Greenbaum technique computes and when it applies. It provides only a tag line plus billing/group info, leaving an agent unable to distinguish this from the many other Hellenistic quality/timing tools without opening schemas.

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?

Four required parameters (date, time, latitude, longitude) are self-evident from names and schema constraints, and the schema documents timezone, ayanamsa, and precision in depth. However, 33% schema coverage means roughly two-thirds of the 15 params, including houseSystem, zodiacType, and cosmogram, carry no description anywhere; the description does nothing to compensate.

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 one-line purpose, 'Synchronistic quality of a moment', is cryptic jargon that doesn't state what computation occurs or what the agent gets back. It restates the title rather than describing a verb+resource. The only concrete information is administrative (group/cost) and the alias relationship, which is structural metadata, not purpose.

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?

There is no guidance on when to use this tool versus the canonical astroway_hellenistic_greenbaum_quality_of_time, nor versus siblings like the daimon/tyche, sect, or planetary-hours tools. The alias note tells the agent the tool exists but not when to prefer it, and no conditions, prerequisites, or exclusions are given.

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