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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and mutability are covered. The description adds genuinely useful non-schema facts: the endpoint, the group, and a 10-credit Tier 1 cost, which matters for call budgeting. It stops there, disclosing nothing about computation latency or output size.

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 description is compact, front-loads the content list, and uses bracketed metadata lines that are easy to scan. No sentence is padded, though the opaque 'JWG' prefix spends characters without informing the 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?

An output schema exists, so return structure need not be explained, and the annotation set covers the safety profile. What is missing is the interpretive context a 10-credit specialized astrology call warrants: what 'ruler' and 'hard aspects' resolve to, and how this differs from the other evolutionary endpoints. Adequate but thin for a 15-parameter tool.

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?

With 15 parameters and only 33% schema description coverage, the description must compensate, and it does not. Its [Required: date, time, latitude, longitude] line merely restates the schema's required array and adds no format, unit, or default guidance. Cryptic inputs like the single-letter houseSystem codes and the bare cosmogram boolean are left entirely undocumented by both the description and the schema.

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 string "Pluto sign+house+ruler+hard aspects" does name the resource and the four outputs produced, so the agent can infer this computes a natal Pluto condition. But there is no verb, and the leading "JWG" is unexplained jargon that carries no meaning for an agent unfamiliar with Jeffrey Wolf Green's school. Differentiation from evolutionary siblings (nodal_axis_detail, skipped_steps, soul_types) is only implicit via the word 'Pluto'.

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?

The description gives no when-to-use, when-not-to-use, or alternative-tool guidance. Nothing tells the agent whether this Pluto condition should be requested alone or alongside the nodal axis / skipped steps calls in the same Evolutionary Astrology group. Only the group tag hints at context.

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