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

Annotations already declare the read-only, idempotent, non-destructive behavior. The description adds useful operational context beyond annotations: group, cost (10 credits, Tier 1), and alias relationship. It does not cover auth needs or rate limits, so it falls short of maximum.

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?

Short and front-loaded: calculation purpose first, then system/group/cost/alias details. Every line adds useful selection or operational context without filler.

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?

For a simple calculation tool with an output schema and strong annotations, the description covers system, cost, and alias identity. It still leaves the required `name` parameter unexplained and does not route among the many numerology siblings, but the core call context is mostly complete.

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 50%; `fields` and `precision` are already described in the schema, and `date` has a pattern. The description reinforces `date` as a birth date reduced from year/month/day, but it never explains the required `name` parameter, so it only partially compensates for the coverage gap.

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?

States a specific verb (Calculate), resource (Life Path number), input (birth date), and system (Kabbalistic Mathers strict). It also names the canonical tool it aliases, which helps distinguish it from the many numerology siblings.

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 supplies clear selection context via the system name, group label, and credit cost. However, it does not explicitly say when to choose this over other Life Path variants, such as Pythagorean, Chaldean, or non-strict Kabbalistic tools.

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