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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds the credit cost (10 credits, Tier 1), which is genuinely useful for an agent budgeting calls, but nothing about determinism of results or what the computation depends on.

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?

Two short lines, front-loaded with the action and followed by group/cost metadata. No filler, though the bracketed tags are boilerplate rather than description content.

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?

An output schema exists, so return values need not be described. However, for a 4-parameter tool with two undocumented required parameters, the description leaves the role of `date` and the handling of multi-part names unaddressed — enough to call it, not enough to call it confidently.

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 50%: `fields` and `precision` are documented in the schema, while `name` and `date` aren't. The description only implicitly clarifies that `name` is the full name being reduced; it never explains why a birth `date` is required for an initials-based calculation, so it fails to compensate for the uncovered required parameters.

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 (Calculate) and resource (the Balance number) plus the method used ('from initials of each part of the full name') and the system ('Vedic'). It distinguishes itself from the Chaldean/Kabbalistic/Pythagorean balance siblings via the system tag, though the differentiation relies on the bracketed tag rather than prose.

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 statement of when to choose this over the ~60 sibling numerology tools, and no prerequisites or exclusions. The agent must infer from the name that this is the Vedic-variant balance calculator.

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