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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds only the credit cost (10 credits, Tier 1), which is mildly useful, but says nothing about what the computation actually yields or any constraints on core required inputs like date/time/lat/long.

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 fragments, no waste in the literal sense, but also no substance — this is under-specification rather than conciseness. The credit/group metadata is front-loaded while purpose is absent.

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 15-parameter astrological computation with a required date/time/latitude/longitude core, the description omits what the tool produces and how it differs from its many siblings. An output schema reduces the need to document returns, but nothing here addresses invocation or selection.

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 only 33% across 15 parameters, so the description is obligated to compensate and does not — it mentions no parameter at all. Fields like ayanamsaId, cosmogram, zodiacType, houseSystem, and name/city defaults are left to the schema alone.

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 merely restates the title ('Arroyo's evolutionary cycle' vs 'Arroyo: Cycle of Becoming') without a specific verb or resource. It never says what the tool computes or returns, so an agent cannot distinguish it from the many sibling cycle-of-becoming tools (rudhyar_cycles_of_becoming, psya_cycle_of_becoming).

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 when-to-use guidance, no exclusions, and no mention of the competing siblings despite a large cluster of near-identical tools. The only added information is a group label and a credit cost, neither of which helps selection.

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