Balance (pythagorean)

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

Annotations indicate readOnly and idempotent, but the description implies a name parameter not in schema. No explanation of how location parameters affect calculation. Contradicts annotations by suggesting a write-like operation (calculating from name) that doesn't align with schema.

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?

Short but includes a misleading example request body that doesn't match the schema. The description is not well-structured and wastes space on incorrect information.

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?

No output schema, yet the description does not explain what the tool returns. It also fails to reconcile the discrepancy between the described input (name) and actual schema (date/location). Leaves many open questions.

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 description introduces a non-existent parameter (name) and fails to clarify the role of latitude, longitude, and timezoneOffset. Despite 100% schema coverage, the description adds confusion rather than value.

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 states it calculates the Balance number from initials, but the input schema does not include a name field, only date and location. This contradiction undermines clarity.

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 guidance on when to use this tool versus siblings like numerology_pythagorean_birthday. No context for choosing among many similar numerology tools.

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