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

Annotations already cover the read-only, idempotent, non-destructive safety profile, so credit is for added context. The description adds that the computation uses all letters of the full birth name and reduced values, and it discloses a 10-credit cost, which is useful behavioral information beyond the annotations.

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?

Front-loaded with the core calculation, followed by a compact system tag and cost line. Very little waste, though the system label partially duplicates the title and group metadata.

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?

Output schema and annotations carry return format and safety obligations, so the description does not need to restate them. It supplies the essential computation, input expectation for name, system, and cost, leaving only usage guidance and date semantics unaddressed.

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 description coverage is 50%, with the optional fields and precision parameters documented in the schema. The description partially compensates by clarifying that the name parameter should be the full birth name with all letters used, but it does not add explanation for the required date parameter beyond the schema pattern.

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), resource (Expression/Destiny number), input (full birth name letters), and system (Vedic). This clearly distinguishes it from the many nearby siblings such as pythagorean_expression, chaldean_expression, and vedic_life_path.

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 the other expression calculators or other Vedic numerology tools. The group and cost tags identify context but do not tell the agent when this choice is appropriate.

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