Arroyo — Element Balance

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

Annotations already mark the tool as read-only and idempotent. The description adds no behavioral context, such as what computations occur or what the output represents, despite having the burden to do so.

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 description is extremely brief (one phrase plus group label), which is concise but sacrifices usefulness. It is front-loaded but lacks substantive content to justify its brevity.

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?

Given the tool's 11 parameters, 2 required fields, and no output schema, the description provides almost no context on how to use it or interpret results. It fails to meet the needs of a complex astrological tool.

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 0% schema description coverage, the description must explain parameter meaning but fails entirely. The example placeholder '{"...chart":"..."}' offers no semantic insight, leaving all 11 parameters unexplained.

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 'Element distribution and integration' is vague and does not specify what kind of element or what the tool computes. It fails to differentiate from the similar sibling tool 'modern_arroyo_element_integration', providing no unique purpose.

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 guidance is given on when to use this tool versus alternatives like 'modern_arroyo_element_integration' or 'modern_arroyo_relational_element_map'. There is no mention of prerequisites or contexts.

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