Destiny Matrix — Ladini Method

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

Annotations already indicate safe, read-only, idempotent behavior. The description adds that it returns arcana with full meaning structure, which matches the annotations and provides useful behavioral context beyond the safety profile.

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 concise at two sentences plus metadata lines. It front-loads the core purpose and output details without unnecessary wording. Every piece of information serves a clear purpose.

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?

The description covers the output (full 22-position matrix with arcana types), the required input (date), and includes cost and group context. It does not explain the optional location/timezone parameters, but those are in the schema. Overall, it provides sufficient completeness for an agent to understand the tool's capability.

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% so all parameters have descriptions in the schema. The description only mentions 'birth date' and shows an example with just 'date', but does not explain the optional latitude, longitude, and timezoneOffset parameters. The schema already does that, so the description adds minimal semantic value.

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 a Destiny Matrix via the Ladini method from a birth date, and lists the specific outputs (centre arcanum, body positions, soul positions, karmic and resource arcana with meaning structure). This distinguishes it from sibling tools which are diverse but mostly unrelated to this specific matrix method.

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 a group label ('Destiny Matrix'), a cost note, and an example request, giving context on when to use it. However, it does not explicitly compare to alternative matrix methods or specify when not to use it.

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