Get Numerology Report

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

Since no annotations are provided, the description carries the full burden. It discloses that the tool returns both structured text and a PNG image, and states it is deterministic. It does not explicitly state it is read-only, but for a get/calculator tool it is implied. Additional context like side effects or rate limits is not needed for this type of tool.

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 two efficient sentences in Korean. Every piece of information is useful: inputs, calculation details, output format, and methodology. No unnecessary words or repetitions.

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 the tool has no output schema, the description adequately explains the return values (structured text and PNG). It covers all necessary aspects: input requirements, calculation scope, and output form. For a simple numerology calculator, this is complete.

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 description coverage is 100% with each parameter having a description. The tool description adds value by clarifying that the name must be in Latin alphabet and provides an example (Hong Gildong), which goes beyond the schema's description. This helps the agent properly format the input.

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 takes a name (Latin alphabet) and birthdate, calculates specific numerology core numbers including master/karma numbers, and returns structured text and a summary PNG. It specifies the Pythagorean method and deterministic nature, leaving no ambiguity about what the tool does.

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 explicit when-to-use or alternatives are mentioned, but with no sibling tools, this is less critical. The description provides clear input format guidance (Latin alphabet for name, date format) and specifies the method (Pythagorean), which helps the agent decide if this is the right numerology tool.

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