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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: the 10-credit cost and the domain detail that the number activates around age 35. It does not describe output format, but an output schema exists.

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 is three short lines: a front-loaded purpose statement, then group and cost metadata. Every sentence earns its place with 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 two required parameters, the description covers the core purpose, system, and cost. It is slightly incomplete because it does not clarify the name/date parameters or provide usage context against the many sibling tools.

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 only 50% (date and name lack descriptions), so the description should compensate. It provides no information about the name, date, or their expected formats, leaving the agent to infer from schema patterns alone.

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?

The description states a specific verb (Calculate), resource (Maturity number), and system (Chaldean), and defines the concept as the sum of Life Path and Expression. This clearly distinguishes it from sibling maturity tools in other numerological systems (Kabbalistic, Pythagorean, Vedic).

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 'Numerology: Chaldean system' label and group tag imply the tool's context, but the description gives no explicit when-to-use or when-not-to-use guidance, nor does it name alternatives. The 'activates around age 35' note is domain context, not invocation guidance.

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