Maturity (pythagorean)

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

Adds useful behavioral context by mentioning the number activates around age 35, but does not contradict annotations (readOnlyHint=true). The description adds moderate extra value beyond 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?

Reasonably concise with front-loaded action verb, but the inclusion of an irrelevant 'name' parameter in the example and lack of structured formatting reduce clarity.

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?

Missing essential information: no output schema to describe return value, no explanation of optional parameters, and the example introduces an extraneous parameter. This leaves the agent with significant uncertainty about the tool's behavior.

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 example request body includes "name" which is not in the input schema, potentially misleading the agent. Schema parameters have 100% coverage, but the description does not clarify the purpose of latitude, longitude, or timezoneOffset for this calculation.

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?

Clearly states the tool calculates the Maturity number (sum of Life Path and Expression) and specifies the Pythagorean system, distinguishing it from other numerological maturity tools. However, it could more explicitly differentiate from other Pythagorean numerological numbers.

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 no guidance on when to use this tool versus alternatives (e.g., other Pythagorean numbers or maturity numbers from other systems). Lacks context for agent decision-making among numerous sibling tools.

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