ExternalFulfillmentReturns_listReturns

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

With no annotations provided, the description carries the full transparency burden. It does disclose an important execution trait—'Runs in your Kuudo deployment, not here'—and 'Retrieve' implies a read-only operation. However, it omits pagination, response structure, authentication, rate limits, and possible scoping details, so transparency is only partial.

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 meaningful content is compact: one clause for environment and one for purpose. The leading 'Catalog entry.' is noise that does not help an agent select or invoke the tool, so the description is not perfectly economical.

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 zero-parameter list operation, the description gives the essential action and deployment context. It is usable but thin: no output schema exists, yet the description does not describe response shape, ordering, or limits, and the 'Catalog entry.' label adds ambiguity.

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 is empty and the context reports 0 parameters with 100% schema coverage, so there are no parameter semantics to document. The baseline of 4 applies because no parameters can create ambiguity. The description adds nothing about the permissive additionalProperties:true field, but that field is not a documented parameter set.

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 core sentence 'Retrieve a list of return items' states a clear verb and resource. The list scope distinguishes it from the sibling ExternalFulfillmentReturns_getReturn, though the description does not explicitly name that alternative. The opening 'Catalog entry.' adds no semantic content and slightly muddies the 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 choose this tool over getReturn or any other returns/shipping tool. The only contextual note, 'Runs in your Kuudo deployment, not here,' is an environment constraint rather than usage direction. The agent is left to infer when a bulk list of return items is needed.

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