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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not carrying that burden. It adds the credit cost (10 credits, Tier 1) and the HTTP endpoint, which are genuinely useful decision inputs not present in structured fields. It does not describe latency, failure modes, or what the returned date/body looks like.

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 concept is front-loaded in one dense, well-formed sentence, followed by a compact bracketed metadata block. There is little wasted text, though the required-parameters line duplicates the schema's required array and adds no information.

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, three enums of non-obvious values, and only 33% schema coverage, the definition is thin for a tool of this complexity. An output schema exists, so return values need not be explained, but the description never clarifies how the many optional configuration parameters affect the computed Design date, nor whether they matter for this endpoint at all.

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%, so the description must compensate, and it does not. It merely repeats the four required parameters already declared in the schema's required array, leaving cryptic optional inputs such as houseSystem (single-letter enum values P, K, R...), zodiacType, cosmogram, ayanamsaId and fields unexplained.

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 gives a specific verb (Find) plus a precisely defined resource: the Design date, explicitly glossed as 'the moment 88° of solar arc before birth' and 'the unconscious imprinting point'. That is far more than a restatement of the name. It does not, however, distinguish this from siblings such as astroway_hd_human_design, which likely also surfaces a Design date.

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 statement of when to use this tool versus the many HD siblings, nor any prerequisites or exclusions. The bracketed block lists required params and cost, which is operational metadata rather than usage guidance. An agent must infer the use case entirely from the concept definition.

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