Hologenetic Profile

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

Annotations already provide readOnlyHint=true and idempotentHint=true, indicating safe read behavior. The description adds cost (50 credits) and an example request but does not disclose other behavioral traits like dependencies on prior chart calculations or error handling.

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 description is short (3 sentences) and front-loaded with purpose. Group and cost info are useful. The example is helpful but could be integrated more cleanly. Overall efficient.

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 11 parameters, 2 required, and no output schema, the description is insufficient. It does not explain the output format beyond listing sequences, nor how the input parameters relate to 'HD gate activations'. Missing details on validation or prerequisites.

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 coverage is 0%, placing full burden on description. Only an example request is provided for 5 of 11 parameters; the remaining 6 (name, city, houseSystem, zodiacType, ayanamsaId, cosmogram) are unexplained. The description fails to compensate for missing schema descriptions.

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 clearly states the verb 'Calculate' and the resource 'Gene Keys hologenetic profile' with specific sequences. It differentiates from generic Human Design tools by focusing on Gene Keys, but does not explicitly distinguish from sibling HD tools like hd_circuitry.

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 guidance on when to use this tool vs alternatives like human_design or hd_circuitry. The description implies input of HD gate activations but does not clarify how the provided date/location inputs relate to that, leaving usage ambiguity.

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