Hyleg & Alcocoden

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds minimal value by confirming it's a calculation, but does not disclose any additional behavioral traits like prerequisites or output format.

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 and front-loaded with the action. The example request is helpful, though the metadata (group, cost) adds structure. It is efficient with no wasted words.

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 no output schema and 11 parameters at 0% explanation, the description is incomplete. It does not describe the return value or the function of optional parameters, leaving significant gaps for the agent.

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% and the description does not explain any parameters beyond providing a single example. Many parameters like houseSystem, zodiacType, ayanamsaId are left undocumented, forcing the agent to guess their meaning.

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 tool calculates Hyleg and Alcocoden using a traditional Hellenistic method, with a specific verb ('Calculate') and resource ('Hyleg and Alcocoden'), distinguishing it from other Hellenistic tools like hellenistic_hand_longevity_hyleg.

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 versus alternatives, such as hellenistic_hand_longevity_hyleg. The description lacks when-to-use or when-not-to-use context, forcing the agent to infer from the name alone.

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