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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds the price tier (10 credits, Tier 1), which is genuinely useful behavior not present in annotations, but says nothing about determinism, latency, or what the profile contains beyond a one-line summary.

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?

One tightly written sentence that front-loads the computed content, followed by short group/cost metadata lines. Nothing is padded, though the metadata lines are boilerplate rather than substance.

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 explained, and the annotations cover the safety profile. Still, for a 15-parameter calculation tool with low schema coverage, the definition leaves the input side thin and provides no guidance on the tropical/sidereal, house-system or timezone choices an agent must make before calling.

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 only 33% across 15 parameters, so the description carries a compensation burden it does not meet: it mentions no inputs at all. Several parameters (timezone, timezoneOffset, ayanamsa, precision, fields) carry their own schema prose, but the description adds no semantics, defaults, or hints about which inputs matter for this profile.

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?

The description names a specific computed artifact: an element profile over the luminaries plus Mercury/Venus/Mars, with a dominant element and strengths/vulnerabilities/coping. That is a clear verb+resource, and it is distinguishable from a generic chart call. It does not, however, differentiate itself from the many sibling element-balance tools (psya_element_balance, arroyo_element_balance, bazi_element_balance), so it falls short of a 5.

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 statement of when to reach for this tool versus the other element or wellness siblings, and no prerequisites or exclusions. The only orienting information is the group tag (Wellness) and the credit cost, which tells cost but not applicability.

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