Number Meaning

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful context by stating it is standalone and provides a link to the full output and error contract, supplementing the annotations with additional behavioral clarity.

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 structured into clear sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH) and includes a link to full documentation. While it repeats some schema information (e.g., number range, response_format), the repetition is minimal and serves to reinforce key constraints without excessive verbosity.

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?

Given that an output schema is present, the description does not need to explain return values. It provides sufficient context: the purpose, input constraints, differentiation from siblings, and a reference to the full contract. This is complete enough for an agent to decide when and how to invoke the tool.

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 coverage is 100%, so the baseline is 3. The description adds value by specifying the exact inclusive range (1-33) and the error condition (INVALID_PARAMS) for the number parameter, and clarifies the meaning of the response_format enum, going beyond the schema descriptions.

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 returns dictionary-style numerology copy for a single integer, including interpretation and keywords. It explicitly distinguishes itself from similar sibling tools (asterwise_get_numerology_profile and asterwise_get_lucky_numbers) in the 'DO NOT CONFUSE WITH' section, making its unique purpose unambiguous.

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 provides explicit guidance on when not to use this tool by naming the alternatives and their differences. It also outlines the input contract (inclusive range 1-33 and error behavior) and mentions output format options, giving clear instructions for correct invocation.

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