Arroyo — Element Integration

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the tool is safe and idempotent. The description adds no behavioral context (e.g., what output to expect, whether it requires authentication, or any side effects beyond the annotations).

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 short but under-specified. It lacks structure, useful headings, or a clear breakdown. The example is malformed and unhelpful. Conciseness should not come at the cost of essential information.

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 complexity (11 parameters, no output schema, 0% schema coverage), the description fails to provide even minimal context about what the tool returns, how parameters relate, or what 'strategies for integrating weak elements' entails. The example is confusing, making the tool nearly unusable without external knowledge.

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 compensate. It only provides a broken example '{...chart:...}', which fails to clarify any of the 11 parameters (e.g., date, time, location, house system, etc.). No parameter meanings are conveyed.

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 'Strategies for integrating weak elements' is vague and does not specify what the tool does with a clear verb and resource. It does not distinguish it from sibling tools like modern_arroyo_element_balance or interpret_element. The example request body is incomplete, offering no clarity.

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 provided on when to use this tool versus its siblings or other element-related tools. There is no mention of context, exclusions, or alternatives, leaving the agent to guess the appropriate use case.

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