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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds genuinely useful operational context beyond that: the POST endpoint, the required inputs, and the 10-credit Tier 1 cost, which matters for an agent deciding whether to spend a call.

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 prose is a single efficient sentence and the bracketed metadata block is compact and scannable. Nothing is padded, though the metadata lines are largely restatements of structured data.

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?

For a simple read-only calculation with an output schema (so return values need no explanation), the definition covers purpose, cost, and inputs. It falls short on system-selection guidance and on the two undocumented parameters, leaving the agent to guess at the Vedic-vs-other-system choice.

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 only 50%: 'fields' and 'precision' carry their own descriptions, while 'name' and 'date' have none. The description's '[Required: name, date]' merely restates what the schema's required array already declares and adds no format, constraint, or meaning beyond it.

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 four Pinnacle cycles with their age boundaries') and even characterizes the output ('life chapters of opportunity'). The '[Group: Numerology: Vedic]' tag differentiates it from the Chaldean/Kabbalistic/Pythagorean pinnacle siblings, though that differentiation comes from metadata rather than the prose itself.

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?

There is no when-to-use guidance: nothing says when to pick Vedic pinnacles over vedic_chart, vedic_life_path, or the Chaldean/Kabbalistic pinnacle variants. The agent must infer selection purely from the tool name.

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