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

Annotations already cover readOnly/idempotent/non-destructive. The description adds genuinely new behavioral context: the credit cost (10 credits, Tier 1) and the domain fact that the number activates around age 35. It also discloses that this is an alias of the longer tool name, which helps an agent avoid double-calling.

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?

Front-loads the definition in one tight sentence, then uses bracketed metadata lines for group and cost and a parenthetical alias note. Every element is load-bearing; no 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?

An output schema exists, so return values need no explanation, and the description supplies cost, system identity, and the alias. The only gap is routing guidance among the near-identical sibling systems, which is a minor omission for a simple two-required-param computation.

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` carry descriptions, while `name` and `date` are undocumented but self-evident (date has a strict YYYY-MM-DD pattern). The description adds no parameter syntax beyond the schema, so 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"), defines the quantity (sum of Life Path and Expression, activates ~35), and names the exact system (Kabbalistic, Mathers strict). This differentiates it from the many sibling maturity tools (chaldean, pythagorean, vedic, plain kabbalistic).

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 system tag "[Group: Numerology: Kabbalistic (Mathers strict)]" implicitly routes the agent, but there is no explicit when-to-use guidance or comparison against the sibling systems. An agent must infer that 'strict' should be chosen over plain kabbalistic.

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