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

The annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds only a cost tier and group label, not meaningful behavioral context such as what the output represents, limitations, or how the past-life method is applied. Cost is useful operationally but does not explain tool behavior.

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 very short and front-loads the method reference, with no filler sentences. However, it is under-specified rather than genuinely concise, and the bracketed tags read more like metadata than helpful structure for an agent.

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 complex tool with 15 input parameters, 4 required fields, and low schema description coverage, the description is drastically incomplete. It provides no explanation of inputs, output, usage context, or how this differs from sibling tools, leaving the agent with almost nothing beyond the annotations and title.

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?

The schema description coverage is only 33%, and the description provides no parameter guidance whatsoever. Required inputs like date, time, latitude, and longitude are undocumented in the description, and optional parameters such as zodiacType, houseSystem, and cosmogram are not explained. The description fails to compensate for the low schema coverage.

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 astrological technique (Forrest 2008 past-life method), which gives some sense of the domain. However, it never states what the tool actually computes or returns, and it does not distinguish this from sibling evolutionary astrology tools such as skipped steps or nodal axis detail. An agent would still have to infer the purpose from the title and group.

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 alternatives. The group tag 'Evolutionary Astrology' and cost tag imply a specialized context, but no explicit conditions, exclusions, or sibling routing are provided.

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