ExternalFulfillmentShipments_retrieveInvoice

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

With no annotations, the description carries the full behavioral burden. It discloses that execution happens in a Kuudo deployment rather than locally, which is useful, but it does not describe return values, authentication needs, error behavior, or how the shipment is identified. The word 'retrieve' implies read-only, but the description leaves major behavioral unknowns unresolved.

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 short and contains only three sentences, each providing some context: catalog status, deployment location, and the operation. It is not front-loaded with the action, but it is economical and does not waste words.

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 no annotations, no output schema, and an empty input schema, the description is not complete enough for an agent to invoke the tool correctly. It provides a deployment hint but omits the shipment identifier mechanism and expected response, leaving a significant gap between the stated operation and practical usage.

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?

The input schema declares zero properties but allows additionalProperties. The description says 'for the shipment you specify,' implying a shipment identifier parameter, yet no parameter name, type, or format is documented. With 0 parameters, the description should compensate, but it does not explain how to specify the shipment.

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 a clear verb and resource: 'Retrieve invoices for the shipment you specify.' This makes the core operation understandable. However, it does not differentiate this tool from the sibling ExternalFulfillmentShipments_generateInvoice, and the 'Catalog entry... not here' framing adds ambiguity about whether the tool is actually invocable.

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?

The description gives a deployment caveat ('Runs in your Kuudo deployment, not here') but no guidance on when to choose this tool over alternatives such as ExternalFulfillmentShipments_generateInvoice or ExternalFulfillmentShipments_getShipment. There are no conditions, prerequisites, or explicit exclusion statements to help an agent select it correctly.

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