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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the cost (20 credits, Tier 2), which is genuinely useful behavioral context, but says nothing about return contents, required chart state, or limits. With annotations carrying the safety burden, this is adequate but thin.

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?

A single tight sentence that is front-loaded with the core verb and resource, plus a compact metadata block. Nothing is wasted, though it is arguably too terse 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, and the annotations cover safety. However, for a 15-parameter tool with only 33% schema coverage, the description omits how the chart inputs drive the circuit result and gives no clue about the many optional astrology parameters, leaving the definition at minimum viability.

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 zero parameter meaning — it never mentions date, time, latitude, longitude, or the ayanamsa/zodiac/house-system options. The burden falls entirely on the schema, which leaves several parameters undocumented, 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 verb (analyze) and resource (the 3 Circuits and 6 Sub-circuits in a Human Design chart), and scopes the analysis to activation 'based on defined channels'. That is enough to distinguish it from generic siblings such as astroway_hd_human_design or astroway_hd_penta, though it never explicitly contrasts itself with them.

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 statement of prerequisites (a computed chart / defined channels), and no routing to alternatives among the many HD siblings. The '[Group: Human Design]' tag and cost tier are metadata, not usage guidance.

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