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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the POST endpoint, credit cost (20 credits, Tier 2), and grouping, letting the agent reason about budget and scope. It does not describe computation nuances, but the output schema covers return values.

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?

Front-loaded single sentence stating the purpose, followed by compact metadata lines (group, endpoint, required, cost). Nothing is padded, though the bracketed metadata is boilerplate rather than description prose.

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?

With 15 parameters and low schema description coverage, a complex HD computation tool, and many sibling tools, the description is thin: it omits which optional parameters matter, how chart inputs interact, and how this output relates to other HD endpoints. The existing output schema and annotations cover returns and safety, but the parameter and routing gaps leave it under-specified.

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 should compensate. Instead it merely restates the four required parameters (date, time, latitude, longitude) that the schema already marks required, adding no meaning for the 11 optional parameters (ayanamsa, timezone, fields, precision, houseSystem, zodiacType, etc.).

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 states a specific verb ('Analyze') and resource ('Circuits and Sub-circuits activated in a Human Design chart'), including the enumeration of 3 circuits and 6 sub-circuits and the basis ('defined channels'). It is distinguishable from related HD siblings, though it does not name which sibling reads the underlying channels/hologenetic data, so the boundary is implicit rather than explicit.

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 statement of when this is preferable to siblings such as astroway_hd_hologenetic or astroway_hd_human_design, and no prerequisites or exclusions. The only situational information is the required-parameter and cost metadata, which is not usage guidance.

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