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 and the alias relationship — but says nothing about what the analysis computes or what constraints apply.

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 definition is short and front-loads the one substantive phrase; the bracketed group/cost/alias lines are compact and each carries information. Nothing is padded, though the metadata blocks crowd out any real functional 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 not be described, but for a 15-parameter chart-calculation tool with low schema coverage the description omits everything an agent needs: what an element balance report contains, how it differs from the integration sibling, and how the required date/time/coordinate inputs drive the result.

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?

With 15 parameters and only 33% schema description coverage, the description carries a heavy compensating burden and supplies nothing — no explanation of date/time/latitude/longitude requirements, timezone handling, or the compact-mode fields parameter. The undefined parameters (city, name, cosmogram, zodiacType, houseSystem, ayanamsaId, etc.) are undocumented in both places.

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?

"Element distribution and integration" largely restates the name and title ("Element Balance") rather than naming a specific operation, input, or output. It gives no verb (compute/generate/analyze) and no mention of a natal chart, so an agent cannot distinguish it from the sibling astroway_psya_element_integration or relational_element_map.

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 use this tool versus the many sibling psychological/Arroyo tools, nor any prerequisites or exclusions. The only routing hint is that it is a 'cursor-friendly alias' for astroway_psychological_modern_arroyo_element_balance, which helps deduplicate but does not explain when this analysis is the right choice.

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