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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description does add non-obvious operational context the annotations cannot: the 10-credit Tier 1 cost, the required input quartet, and the fact that this is a cursor-friendly alias of the fully-named endpoint. It discloses nothing about computation or result content, so it earns moderate rather than high credit.

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 single fragment plus the bracketed metadata block is front-loaded and free of padding, so nothing is wasted. However the terseness is under-specification rather than true conciseness, and the useful metadata (endpoint, cost, alias) is tucked below the near-empty headline sentence.

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-computation tool this is far too thin. An output schema exists, so return values need not be described, and annotations cover safety, but the description never says what the tool computes, what tradition-specific output to expect, or how the alias relates to the canonical endpoint.

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%, so the description carries a real burden here, yet it only repeats the four required fields already listed in the schema. Parameters such as city, name, cosmogram, zodiacType and houseSystem are undocumented in both places, and the description adds no meaning for any of them.

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 is the fragment "Outer-planet cycles as becoming." It names a subject area (outer-planet cycles) but supplies no verb and no statement of what the tool actually produces, so it largely restates the title "Cycles of Becoming". It also gives no basis for distinguishing it from siblings like astroway_psyr_lunation_phase or astroway_psyr_transits_as_rebirth.

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, when-not-to-use, or alternative-selection guidance anywhere in the text. A reader cannot tell from this description whether to reach for this tool or for the many adjacent Rudhyar/psychological tools.

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