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 usefully adds the credit cost (10, Tier 1) and the alias relationship, which annotations do not convey. It says nothing about output characteristics, though the output schema exists to carry that.

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 reflects under-specification rather than discipline. The bracketed metadata lines (group, cost, alias) are the only structured content, and the one prose sentence is too thin to 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 charting tool with only 33% schema coverage, the description is far too thin; the presence of an output schema excuses it from explaining return values, but nothing covers purpose, usage, or the undocumented parameters. An agent cannot confidently select or configure this tool from the definition alone.

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 carries a heavy compensation burden — and it supplies none, mentioning no parameter at all. Several params (fields, timezone, precision, timezoneOffset) are self-documented in the schema, but required params like date/time/latitude/longitude and enums like houseSystem/zodiacType remain unexplained in the description.

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 reduces to "Arroyo's evolutionary cycle," which essentially restates the title "Arroyo: Cycle of Becoming" without naming a verb or saying what is computed or returned. It does not distinguish this tool from the many sibling psychological/astrology tools (element_balance, cycles_of_becoming, etc.). The only concrete routing information is that it is a Cursor-friendly alias of another tool.

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 statement of when to use this tool versus its alias twin `astroway_psychological_modern_arroyo_cycle_of_becoming` or the sibling psychological analyses. The group label and cost tier are metadata, not usage guidance. An agent is left to infer the selection criteria entirely.

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