HD Group Overlay

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description's 'Calculate' aligns with these. It adds the cost (100 credits) but otherwise provides no additional behavioral context beyond what annotations offer.

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 a single sentence plus metadata (Group, Cost) and an example. It is concise and well-structured, but the lack of an output schema or further details slightly detracts.

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?

There is no output schema, and the description does not explain what the tool returns (e.g., format of centers and channels). For a complex tool like HD group overlay, this omission leaves the agent uncertain about the output structure.

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 0% per context signals. The description does not explain parameter semantics; it only provides a JSON example. The schema itself has some descriptions inside the items property, but the tool description adds no value beyond that.

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 resource 'HD group overlay chart' for 2+ people, specifying 'collectively defined centers and channels'. This distinctively separates it from sibling tools like 'group_synastry' and 'human_design_compatibility'.

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?

The description provides an example request but gives no guidance on when to use this tool versus alternatives like 'group_synastry' or 'human_design_compatibility'. No explicit when/not-to-use instructions.

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