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

Annotations already mark it read-only and non-destructive. The description adds meaningful extra behavioral detail: it automatically detects Master Numbers and returns interpretative results in the specified manner and depth. It does not contradict the annotations and goes beyond the annotation-only safety profile by describing useful operational behavior.

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 front-loads the core purpose and computation, then gives output type, scope, and master number behavior. It avoids overly deep structure, but retains a few promotional contextually less central phrases. There is minor redundancy with the title, but the definition preserves useful detail without exceeding the intended.

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?

There is no output schema, so the description fills that gap by describing the returned interpretation and rough length. It also covers Master Numbers and the domain. It gives an agent enough info to know what inputs will do, what output to expect, and whether this is the right tool for a general request about later life or maturity.

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?

The schema covers all parameters clearly, and the description adds a layer not visible in the schema: that the two central inputs (Life Path and Expression) are combined to produce the Maturity number. This helps an agent understand why both parameters exist and how the computation algorithm is structured, beyond the basic 'birth date' versus 'direct number' guidance.

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?

Description opens with a specific verb and resource: 'Calculate your Maturity (Realization) number by adding Life Path and Expression numbers using Pythagorean numerology.' It clearly defines what the tool computes and why it differs from sibling tools that only compute Life Path or Expression numbers, by presenting the combination and later-life focus.

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?

Clearly establishes the use case by describing when the Number manifests, that it is relevant for midlife guidance, and which application types should use it. It does not name alternatives or explicitly state when not to use this tool, but it is directional enough for an agent to route to it for maturity-focused calculations.

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