ZR from Fortune

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the tool is read-only and idempotent. The description adds nothing beyond that; it does not mention error handling, input validation, or what happens with missing/invalid chart data. There is no contradiction with annotations.

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 very concise: a single line plus a group tag and example. It is front-loaded with the key purpose. However, it could include a brief usage note without sacrificing conciseness. Overall well-structured for its brevity.

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?

Given the complexity of zodiacal releasing and the absence of an output schema, the description is incomplete. It does not describe the output format, interpretation of periods, or how the 'years' parameter affects results. The siblings list is large but no cross-referencing is provided.

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 100% and the schema already includes a description for the birth data parameter, including defaults and requirements. The tool description does not add any additional meaning about parameters beyond what the schema provides, so it meets the baseline.

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 states 'Zodiacal Releasing from Lot of Fortune — body/livelihood periods', which clearly indicates the tool computes ZR for the Lot of Fortune focusing on body/livelihood. This distinguishes it from the sibling 'hellenistic_brennan_zodiacal_releasing_spirit' (spirit periods). However, it does not explain what zodiacal releasing is, leaving some ambiguity for unfamiliar agents.

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 no guidance on when to use this tool versus its siblings (e.g., spirit version, loosing of bond, peak periods). It only mentions 'body/livelihood periods' without explaining the context or prerequisites for choosing this variant.

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