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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds the credit cost (10 credits, Tier 1), which is genuinely useful behavioral context an agent cannot get from annotations, but it says nothing about what the 15 lots contain or how results are shaped.

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?

Two short lines with zero filler; the substantive claim is front-loaded. It is arguably under-specified rather than verbose, but nothing in the text is wasted.

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 computation tool with only 33% schema coverage, the description should at minimum say what input it needs (birth date/time/place) and what the 15 lots represent. With an output schema present it need not describe return values, but the input and conceptual gaps leave an agent under-equipped.

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, and the description contributes nothing about parameters. Fields like city, name, cosmogram, zodiacType, houseSystem and ayanamsaId have neither schema descriptions nor description-level explanation, so the description fails to compensate for the coverage gap.

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 deliverable — 'All 15 Hermetic Lots per Brennan §11' — and the group tag situates it in the Brennan tradition, distinguishing it at the family level from the Greenbaum/Hand lot variants in the sibling list. It lacks a verb (compute/derive) and never directly names a competing sibling, but the resource is unambiguous.

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 routing to alternatives such as astroway_hellenistic_hand_lots_of_seven or astroway_aspects_arabic_parts. The only auxiliary text is credit cost and group membership, which do not help an agent choose this tool over a sibling.

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