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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the credit cost and tier, which is genuinely useful non-annotation context, but says nothing about output shape or behavioral limits; 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 core purpose is front-loaded in the first sentence and the metadata tags are compact. It is efficiently sized, though its brevity is closer to under-specification than to disciplined concision given the tool's complexity.

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, but for a 15-parameter tool with 33% schema coverage and a very close sibling the description omits required-input context, usage conditions and sibling differentiation. It is not complete enough for an agent to call it confidently.

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 it does not - it never mentions date, time, latitude, longitude, houseSystem, zodiacType or any other input. Several parameters are documented only inside the schema, leaving the rest undocumented in both places.

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 resource and scope ('Lunar archetypes by sign and house'), so an agent knows roughly what it produces. However it uses a noun phrase with no verb and gives no differentiation from the near-identical sibling astroway_psyg_lunar_myth, so the boundary between them is left to inference.

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 only non-descriptive content is the group tag '[Group: Modern Psychological]' and cost '[Cost: 10 credits (Tier 1)]'. There is no statement of when to prefer this tool over astroway_psyg_lunar_myth or the other psychological-modern siblings, and no prerequisites or input expectations.

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