aruba_get_multicedente_by_id

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, which cover safety and read-only nature. The description adds that it's a GET and returns multiseller details, aligning with annotations but not adding beyond them.

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 concise (one sentence) with no unnecessary words, effectively communicating the core functionality.

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 simple ID lookup with one parameter and good annotations, the description is adequate but not rich. It does not explain what 'multiseller details' include, and given the presence of an output schema, the description could add more context about the return value.

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 only implies the 'id' parameter is a path parameter for the multiseller ID. No additional details on format, range, or validation rules are provided, leaving ambiguity.

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 clearly specifies the HTTP method and path, and indicates it returns read-only multiseller details. It distinguishes from the sibling tool aruba_list_multicedenti by focusing on a specific ID lookup. However, it could be more explicit about what a 'multicedente' is.

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_list_multicedenti or other invoice tools. The agent is left to infer from the tool name and path that it retrieves a single entity by ID.

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