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 covered. The description adds genuinely useful non-schema context — the 10-credit Tier 1 cost — but says nothing about output shape, auth, or rate limits. With annotations doing the heavy lifting, a 3 is fitting.

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 the grouping/cost metadata. No wasted sentences, though the bracketed metadata is 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 no explanation, and annotations cover safety. What remains missing is guidance on selecting this school over its many siblings and any rationale for the required 'name' parameter. Adequate but with clear gaps for a tool in such a crowded namespace.

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 self-documented in the schema, while required 'name' and 'date' are not. The description clarifies the date semantics ('year + month + day, reduced') but never explains why a required 'name' is needed for a Life Path calculation, nor the expected date format. Partial compensation, so baseline 3.

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 ('Life Path number') with the reduction method (year + month + day) and the school ('Vedic system'). This differentiates it from the large sibling cluster of Chaldean/Kabbalistic/Pythagorean life_path tools, though it doesn't differentiate it from the other Vedic numerology tools it sits beside.

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 no when-to-use or when-not-to-use guidance and names no alternative. An agent choosing between the ~10 near-identical '*_life_path' siblings gets no routing help beyond the school name embedded in the description.

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