Maturity (vedic)

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

Annotations already indicate read-only, idempotent behavior. The description adds that it performs a calculation and mentions activation at age 35, which provides some context beyond annotations. No contradictions.

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?

Description is short with two sentences plus group label. However, the example includes an irrelevant 'name' field, causing potential confusion. It is mostly concise but slightly flawed.

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 tool has 4 parameters (3 optional) and no output schema. The description does not explain how the Maturity number is derived beyond summing two components, nor what the response contains. It fails to justify the need for location/timezone parameters, leaving gaps for an agent.

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?

The input schema has 100% description coverage, so schema already documents parameters. The description does not add value beyond schema and includes an example with an extra field ('name') not present in schema, which could mislead. It also fails to explain optional location parameters' purpose.

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 the tool calculates the Maturity number using Vedic numerology, specifying it is the sum of Life Path and Expression and activates around age 35. It distinguishes from other numerology systems but does not explicitly differentiate from sibling Vedic tools like life_path or expression.

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?

No guidance on when to use this tool versus alternatives. It does not explain scenarios where maturity is relevant or provide any contextual advice. The example request body is provided, but it does not help with selection criteria.

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