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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior. The description adds value beyond them: cost (10 credits, Tier 1), the endpoint, required inputs, and the note that it is a cursor-friendly alias — useful operational context. Return semantics are covered by the output schema.

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 one-line purpose is front-loaded and every bracketed metadata line (group, endpoint, required, cost, alias) carries distinct routing or operational value. Slightly list-heavy but no filler sentences.

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?

With an output schema handling return values and annotations covering the safety profile, the description supplies the remaining essentials: compute inputs, cost, endpoint, and system identity. Only the selection guidance among sibling systems is absent.

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 50%: 'fields' and 'precision' are documented in the schema, while 'name' and 'date' are not. The description only restates the required set, adding no format or meaning beyond the schema, so the 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?

States a specific verb and resource ('Calculate the Maturity number'), supplies the composing formula ('sum of Life Path and Expression'), and pins the exact system ('Kabbalistic (Mathers strict)'). This distinguishes it from the sibling Kabbalistic, Pythagorean, Vedic, and non-strict variants, and the alias line ties it to astroway_numerology_kabbalistic_strict_maturity.

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 explains what the number means ('activates around age 35') but gives no when-to-use guidance or routing among the many maturity/system siblings. An agent is left to infer selection from the group label alone.

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