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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is fully covered. The description adds useful behavioral context not in the annotations: the cost (10 credits, Tier 1) and the domain-specific activation age. No contradictions with annotations.

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?

Two sentences front-load the purpose and formula; metadata lines are compact and non-redundant. No wasted words.

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?

For a simple calculation tool with an output schema and rich annotations, the description covers purpose, formula, system, and cost. It omits parameter-level guidance, but the output schema and annotations relieve that burden. Remaining gap is minor: no explicit routing among alternative numerology systems.

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, but the required `date` and `name` parameters have no descriptions. The description implies both are needed via the formula (Life Path from date, Expression from name), but it does not clarify date format, name expectations, or the roles of the optional parameters. Baseline 3 for partial schema coverage.

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) and resource (Maturity number), plus the exact formula (sum of Life Path and Expression) and the system (Pythagorean). This distinguishes it from the many other numerology maturity tools by naming the system, though it does not explicitly name a sibling alternative. Clear enough for an agent to identify the tool's function.

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?

Provides implied usage context ('activates around age 35') and system grouping, but does not state when to prefer this tool over Chaldean, Kabbalistic, or Vedic maturity siblings, nor any prerequisites or exclusions. Usage is inferred from the name and system label.

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