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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuinely useful non-schema behavior: the endpoint path and a concrete credit cost (10 credits, Tier 1), which an agent needs to budget against astroway_cost_estimate. It does not describe what the method produces, but with annotations carrying the safety burden a 3 is appropriate.

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 the method name is front-loaded, with bracketed metadata that is scannable. But it is essentially a metadata tag block rather than a description, so conciseness here reflects absence of content rather than disciplined editing.

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 needn't be restated, and annotations cover safety. Still, a 15-parameter, 33%-documented tool with only a bare method name and cost is under-specified: an agent cannot tell what the past-life method yields or how it differs from evolutionary 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, so the description is expected to compensate and does not. It merely repeats the four required fields (date, time, latitude, longitude) already listed in the schema, adding no format, default, or interaction guidance.

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?

Names a specific methodology ("Forrest 2008 past-life method") and tags the group "Evolutionary Astrology", which helps distinguish it from the prognostics/cosmobiology siblings. However, it never states what the tool actually computes or returns for the user, so the purpose stays vague to anyone who doesn't already know the Forrest terminology.

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 guidance, no conditions, and no naming of alternative siblings such as astroway_evolutionary_nodal_axis_detail or astroway_evolutionary_soul_types. The metadata block conveys required inputs and cost but nothing about selection.

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