Numerology Profile

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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds useful context about validation failures ('malformed payloads fail upstream') and points to a full error contract via URL, going beyond the annotation baseline without contradiction.

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 (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE), but it is longer than necessary and repeats some schema content (e.g., date format). It earns a 4 for organization and clarity despite minor redundancy.

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?

Fully situates the tool within a large numerological suite by distinguishing it from similar tools, documents its output components, and provides a link to the complete documentation and error contract. An agent has enough context to select and invoke it correctly without ambiguity.

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 descriptions cover 100% of parameters with clear meaning (date format, name conversion, response_format enum). The description itself does not add extra parameter-specific details beyond the schema, so it stays at the baseline warranted by full 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 ('Builds'), resource ('Pythagorean numerology profile'), inputs ('legal name and birth date'), and outputs ('core numbers, cycles, lucky digits, and summary copy'). Explicitly differentiates from Chaldean numerology and lucky-numbers-only tools in the DO NOT CONFUSE section.

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 explicit workflow context (BEFORE/AFTER) naming a related tool and when to use it (to fill Personal Year). Lists alternative tools with clear differentiators, giving unambiguous when-to-use versus when-not-to-use guidance.

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