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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and is a non-open-world tool, so the safety profile is fully covered. The description adds the cost (10 credits, Tier 1) and the concrete endpoint, which is useful but modest context beyond the structured fields.

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?

Purpose is front-loaded in the first sentence, followed by compact bracketed metadata (group, endpoint, required, cost). No filler, and every line carries distinct operational information.

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 not be described, and the description supplies requirements, cost tier and endpoint. It is nearly complete for a read-only calculation tool; only explicit sibling routing is missing.

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%: the 'fields' and 'precision' params carry their own descriptions, while 'name' and 'date' have no schema descriptions. The description only restates 'Required: name, date', which the schema already enforces, and adds no format or semantics beyond that; baseline 3 fits.

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') plus the resource ('Maturity number') and even defines the underlying method ('sum of Life Path and Expression, activates around age 35'). The system qualifier 'Kabbalistic (Mathers strict)' distinguishes it from the many sibling maturity tools (chaldean, pythagorean, vedic, loose 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 group tag and the system label imply when this variant applies versus its siblings, and 'activates around age 35' gives interpretive context. However, there is no explicit when-to-use/when-not statement or named alternative, leaving the agent to infer selection from the system name alone.

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