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 the cost tier ('10 credits, Tier 1'), which is genuinely useful pre-invocation context, but says nothing about what the result contains or how it is scoped.

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?

It is short and free of padding, but the brevity comes from under-specification rather than efficiency: the two lines carry no operational content beyond group and price metadata. Front-loading is moot when there is almost nothing to front-load.

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?

For a 15-parameter astrological computation with an output schema and a large family of near-identical siblings, the description leaves the agent unable to distinguish this tool's output from element_integration or the psya/psyg variants. The output schema excuses it from describing return values, but nothing else is covered.

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 is expected to compensate and does not — it mentions no parameters at all. A handful of the undocumented params (date, time, latitude, longitude, city) are self-evident from name and type, which keeps this above a 1, but the sidereal/house-system options receive no framing from the description.

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 is essentially a restatement of the title 'Arroyo: Element Balance' in other words ('Element distribution and integration'), with no verb, no statement of what artifact is produced, and no differentiation from the many sibling element tools (astroway_psya_element_balance, astroway_psychological_modern_arroyo_element_integration). An agent cannot tell what this computes or how it differs.

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 when-to-use guidance at all: no prerequisites, no conditions, and no routing to alternatives such as the element_integration or relational_element_map siblings that clearly overlap. The only contextual signal is the '[Group: Modern Psychological]' tag, which 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.