aruba_list_multicedenti

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description merely repeats 'Read-only' without adding behavioral context like pagination behavior, data freshness, or any side effects beyond what annotations provide.

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?

Extremely concise (one line), but at the cost of omitting essential information. The brevity leads to under-specification rather than efficient communication.

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?

With 5 undocumented parameters and no output description, the description is severely incomplete. Even though an output schema exists, the description fails to explain what a 'multicedente' is, how filtering works, or pagination behavior.

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 coverage is 0%, and the description provides no explanation for the five parameters (countryCode, vatCode, status, size, page). An agent cannot infer meanings or correct usage from the description alone.

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 states 'Read-only multiseller listing' and the HTTP method GET, clearly indicating a read operation to list multiple entities. It distinguishes from sibling 'aruba_get_multicedente_by_id' (singular). However, 'multiseller listing' may be slightly vague without domain context.

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 on when to use this tool versus alternatives like aruba_get_multicedente_by_id. It does not mention filtering or pagination use cases. The description lacks any contextual hint for appropriate invocation.

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