Maturity Number

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

The annotations (readOnlyHint, idempotentHint, destructiveHint) already cover the key behavioral aspects, and the description is consistent with them. The description adds some context about the calculation process but does not introduce any contradictions, so it slightly adds value beyond the 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?

The description is well-structured with clear sections for workflow, input contract, and distinctions, but it duplicates some information already present in the schema (e.g., the input contract). It is not overly verbose and provides necessary guidance, though it could be slightly more concise.

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?

The description provides sufficient context about the tool's purpose and its relationship to other numerology tools, but the ambiguity around the required/optional nature of the 'date' parameter could lead to misuse. Given the complexity and many sibling tools, this is a notable gap that reduces completeness.

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?

Although the schema covers all three parameters with descriptions, there is an internal inconsistency: the 'date' parameter's description states it 'Defaults to today when omitted' while the required array lists it as required. This ambiguity is not resolved in the main description, creating confusion about whether the date must be supplied.

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 clearly states that the tool calculates the Maturity number, which is the sum of Life Path and Expression numbers, and explains its meaning. It distinguishes itself from similar numerology tools like asterwise_get_numerology_profile and asterwise_get_personal_cycles, providing explicit differentiation.

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 includes a 'WORKFLOW' section that recommends running asterwise_get_numerology_profile first to confirm Life Path and Expression numbers, and a 'DO NOT CONFUSE WITH' section that clarifies differences from two other tools. This gives explicit guidance on when and how to use the tool relative to alternatives.

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