Life Path Number (kabbalistic-strict)

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that the calculation reduces year+month+day and uses the Mathers strict system, but does not provide additional behavioral context (e.g., response format, error handling). With annotations covering safety, this is adequate.

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 two sentences plus a group label and example, all front-loaded with the core action. Every sentence is necessary; no wasted words. Exceptionally concise.

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?

Despite 4 optional parameters (latitude, longitude, timezoneOffset) and no output schema, the description does not explain why location/timezone are accepted, what the return value looks like, or how the reduction works. The tool's complexity demands more detail for an agent to use it fully.

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 the input schema already describes each parameter. The description does not add semantic meaning beyond what is in the schema, though it provides an example usage. Baseline 3 is appropriate.

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 verb ('Calculate'), the resource ('Life Path number'), and the method ('from birth date, reduced'). It also specifies the system ('Numerology — Kabbalistic (Mathers strict)'), which distinguishes it from siblings like the non-strict version and other numerological systems.

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 explicit guidance on when to use this tool versus alternatives (e.g., strict vs. non-strict, or other numerological systems). It lacks direction on prerequisites, exclusions, or context for selection.

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