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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds operational context not present in structured data — the group and the 10-credit (Tier 1) cost — which is genuinely useful, but it says nothing about what the analysis returns or any computation-specific behavior.

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?

It is short and front-loaded, but the brevity comes from under-specification rather than economy. The one substantive sentence conveys almost no information, so the size does not earn its place.

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 chart tool with an output schema and many close siblings, the description is far too thin: it never says what cycles are computed, what the output represents, or how to choose it over the other cycle-of-becoming tools. The output schema relieves it of explaining return values, but the selection and semantics gaps remain.

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 expected to compensate, and it contributes nothing about any parameter. Required birth-data fields are self-explanatory by name, but undocumented options like zodiacType, houseSystem, and cosmogram get no help from either source.

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 phrase "Outer-planet cycles as becoming" is a fragment that largely restates the title "Rudhyar: Cycles of Becoming" and adds only the vague qualifier "outer-planet." It does not state what the tool computes or distinguishes it from near-identical siblings such as astroway_psyr_cycles_of_becoming or astroway_psychological_modern_arroyo_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 prerequisites, and no mention of alternatives. The only added text is a group tag and a credit cost, neither of which tells an agent when this tool is the right choice over the many sibling cycle-of-becoming variants.

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