Birthday (chaldean)

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

Annotations already declare readOnlyHint=true, destructiveHint=false. The description adds no further behavioral details (e.g., error handling, calculation method, or response structure). It does not contradict 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?

The description is concise with two sentences, an example, and a group tag. It is front-loaded with the main action. Only essential information is included.

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 no output schema, so the description should explain the return format. It does not mention what the Birthday number is or that it derives from the day-of-birth digit. The presence of location parameters is unexplained. Completeness is lacking for a simple calculation.

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% with all parameters described. The description adds minor context for 'date' but does not explain why location parameters (latitude, longitude, timezoneOffset) are relevant to a birthday number calculation. The description adds minimal value beyond the schema.

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 verb 'Calculate', the resource 'Birthday number', and the system 'Chaldean'. It provides an example and a group tag, making it distinct from siblings like life_path or expression. The title reinforces the specific system.

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 gives an example but no explicit guidance on when to use this tool versus other numerology tools. It does not state prerequisites or common use cases. The context is implied but not explicit.

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