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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add operational context - and it does, disclosing the cost (10 credits, Tier 1), the HTTP endpoint and the required inputs. It stops short of describing rate limits, auth requirements or the shape of the result, hence not a 5.

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?

Extremely compact and front-loaded: the definitional line comes first, then grouped metadata. No filler sentences, though the bracketed boilerplate ('[Group: ...]') is administrative scaffolding rather than task-relevant content.

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 tool with 33% schema coverage, the description omits the sidereal/tropical choice, house system, ayanamsa defaults and the compact-mode fields/precision options that materially change output. The existence of an output schema excuses it from explaining return values, but not from covering the invocation surface.

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?

Only 4 of 15 parameters are echoed as 'required' and schema description coverage is 33%; the description adds no meaning for ayanamsa, zodiacType, houseSystem, precision, fields or timezone beyond what the schema already says. For a low-coverage schema the description should compensate, and it does not.

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 states the astrological rule the tool encodes ('Planets squaring nodal axis = unfinished karma') and the bracketed metadata supplies the endpoint (POST /v1/evolutionary/skipped-steps), so the domain purpose is inferable. However, it never says what the tool actually computes or returns, and it draws no line between itself and close siblings like astroway_evolutionary_nodal_axis_detail or astroway_evolutionary_pluto_natal_condition.

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 alternative evolutionary tools. The only routing signal is the required-parameter list, which tells the agent how to call it but not when it is the right choice over the four other evolutionary-astrology siblings.

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