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 context the annotations don't: the 10-credit Tier 1 cost and the POST endpoint. It does not disclose determinism of the element result or any error conditions, so it adds moderate value.

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 core sentence is dense and front-loaded, and the bracketed metadata is easy to scan. There is no filler or redundancy. Slightly terse on the qualitative side, but nothing is wasted.

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 cost/endpoint/required inputs are stated. However, for a 15-parameter tool with 67% of parameters undocumented, the description leaves an agent without guidance on the sidereal/house-system optional params or when this tool is preferred over element-balance siblings.

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% (15 params), so the description should compensate for the undocumented ones (cosmogram, zodiacType, houseSystem, name, city). Instead it only repeats the four required parameters already marked required in the schema, adding no syntax, defaults, or meaning for the optional parameters.

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 first sentence names a precise computation (element profile) over specific points (luminaries + Mercury/Venus/Mars) and enumerates the outputs (dominant element, strengths, vulnerabilities, coping). This is far more than a restated title. It stops short of naming which sibling it replaces (e.g. wellness_medical_astrology or psya_element_balance), so it doesn't earn the top score.

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 when-to-use or when-not-to-use guidance. With eight wellness siblings plus many element-balance tools (psya_element_balance, bazi_element_balance, natal element tools), an agent gets no signal on when this profile is the right pick versus those alternatives. Group/endpoint/cost metadata is not usage guidance.

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