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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful context beyond that: the credit cost (10 credits, Tier 1) and the alias relationship. It does not disclose anything about output format, required inputs, or computation, so it is only modestly additive.

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 text is short and front-loads the purpose before the metadata brackets, with no filler sentences. However, for a 15-parameter tool with real complexity, this level of brevity is under-specification rather than effective conciseness. Every sentence earns its place, but too little is said.

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 values need not be explained, and annotations carry the safety profile. But a complex chart-calculation tool with 15 parameters, 4 required, and only 33% schema coverage leaves the agent without the required-input or parameter-selection guidance it needs to call the tool correctly. The definition is materially incomplete for this complexity.

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, well below the 50% threshold, so the description is expected to compensate but adds nothing. It never mentions the four required inputs (date, time, latitude, longitude) or any of the optional astrological controls (ayanamsa, houseSystem, zodiacType, timezone). The schema does carry helpful text on the few documented fields, but the description contributes zero parameter meaning.

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 gives a specific concept ('reframe major transits as rebirth') within Rudhyar psychological astrology, so the domain is identifiable. However, it never states what the tool actually produces or does computationally, and 'reframe' is metaphorical rather than a concrete verb+resource. It does not differentiate itself from the near-identical canonical sibling `astroway_psychological_modern_rudhyar_transits_as_rebirth` beyond the alias note.

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 guidance on when to use this tool versus the many sibling psychological tools (cycles_of_becoming, lunation_phase, symbolic_degrees, etc.). The only routing hint is that it is a 'Cursor-friendly alias' for the canonical name, which tells the agent nothing about the circumstances that should select it.

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