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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful non-annotation facts: the endpoint path and the 10-credit (Tier 1) cost, which the agent cannot learn elsewhere. It does not explain what a 'weak element' calculation depends on or what the response contains.

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 one-line purpose leads, followed by a compact bracketed metadata block. Nothing is padded, though the alias parenthetical and group/endpoint lines are administrative rather than interpretive.

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. However, for a 15-parameter astrological tool with low schema coverage, the description leaves the agent guessing about most optional inputs and how this differs from element_balance.

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. The description merely repeats the four required fields (date, time, latitude, longitude), which the schema already marks required, and says nothing about city, name, cosmogram, zodiacType, houseSystem, or ayanamsaId. It does not compensate for the undocumented portion of the schema.

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 phrase 'Strategies for integrating weak elements' gestures at the output (interpretive strategies for weak astrological elements) but never states a clear verb+resource. It gives no differentiation from the very close sibling astroway_psya_element_balance, relying instead on the alias note to distinguish itself from its long-form twin.

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 statement of when to use this versus astroway_psya_element_balance or the related Arroyo siblings. The only routing information is that it is an alias for astroway_psychological_modern_arroyo_element_integration, which addresses duplicate naming rather than use-case selection.

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