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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavioral context in the form of the credit cost (10 credits, Tier 1) and the endpoint, but does not describe what the calculation returns or any sensitivity of inputs.

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 working sentence is front-loaded and precise, followed by a compact bracketed metadata block. Nothing is padded, though the metadata block is somewhat template boilerplate rather than tool-specific prose.

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 an output schema exists, return values needn't be explained. The description covers purpose, required inputs, endpoint and cost, which is sufficient for calling a read-only calculation endpoint, with only the system-selection reasoning left implicit.

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-schema, while 'name' and 'date' are not. The description partly compensates by naming them as required and clarifying that the name is decomposed into 'each part of the full name' for initials, but adds no format or interpretation detail for 'date' or the compact-mode fields.

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 and resource ('Calculate the Balance number from initials of each part of the full name') and tags the system as 'Vedic', which distinguishes it from the chaldean/kabbalistic/pythagorean balance siblings. It is unambiguous what the tool computes, though it never explicitly contrasts itself with those sibling systems.

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 lists required inputs, group, endpoint and cost, but gives no guidance on when to pick this Vedic balance tool over the chaldean, kabbalistic, pythagorean, or numks/numk balance variants. No prerequisites, no when-not-to-use.

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