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

No annotations are provided, so the description carries full burden. It discloses the 360-day-year convention, level progression (L1-L4), the loop-back and jump rule, and what is returned (timeline or active lords). This sufficiently describes the computational behavior and output, though it does not explicitly state read-only nature.

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 dense paragraph of four sentences that efficiently conveys the core concept, mechanics, and output. It front-loads the technique name and is appropriately sized, though a more structured layout could improve readability.

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 the tool (8 parameters, esoteric technique) and lack of output schema, the description adequately explains what the tool does, its inputs, and its outputs. It covers the technique, conventions, levels, and return values, making it functionally complete for an AI agent to understand its use.

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 100%, so baseline is 3. The description adds context about the technique's mechanics (e.g., Lot defaults to spirit, levels, loop-back) but does not significantly enhance understanding of individual parameters beyond what the schema already provides (e.g., lat, lon, date formats).

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 identifies the tool as Zodiacal releasing (aphesis), a specific Hellenistic time-lord technique from Vettius Valens, and explains its core function of generating a timeline from a Lot. While it does not explicitly contrast with sibling tools like dasha or profections, the unique technique name and detailed description provide sufficient distinction.

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 states that the technique is anchored to the natal Lot and requires exact time and coordinates, implying when to use. However, it does not provide explicit guidance on when not to use this tool versus alternatives, nor does it specify prerequisites or limitations beyond the data requirements.

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