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 genuinely useful operational metadata — the credit cost (10, Tier 1) and group — which the annotations do not convey, but says nothing about how transits are selected or what the reframing means.

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 short fragments, purpose first, no filler words. But the bracketed group/cost tags read as appended metadata rather than prose, and the extreme brevity is under-specification rather than efficiency.

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?

An output schema exists, so return shape needn't be restated, but for a 15-parameter astrological computation with 33% schema coverage and no usage guidance, the description leaves an agent without enough context to invoke it correctly or choose it over its many siblings.

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. The description mentions no parameter at all, so it fails to compensate: notably the four required birth-data fields (date, time, latitude, longitude) and the many optionally-defaulted chart settings are left unexplained beyond the schema text.

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 names a specific operation on a specific object ('Reframe major transits') and echoes the title's Rudhyar/rebirth framing. However, it never says what the reframing actually produces or how it differs from the near-identical sibling astroway_psyr_transits_as_rebirth, or from astroway_psychological_modern_rudhyar_cycles_of_becoming. Vague enough that an agent cannot confidently pick it over its twins.

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?

No when-to-use, when-not-to-use, prerequisites, or alternative is stated. With 40+ siblings including an almost identically named transits-as-rebirth tool, the absence of routing guidance is a real gap.

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