FulfillmentOutbound_listReturnReasonCodes

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

Annotations are absent, so the description carries the full disclosure burden. It does reveal a notable behavioral trait—remote execution in the Kuudo deployment—and 'Returns' implies a read-only list operation. However, it does not mention authorization, error behavior, side effects, or output format. For a simple list/catalog lookup, this is adequate but not deeply transparent.

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 concise at roughly two short sentences and contains no filler. The remote-execution caveat and return scope are both included. The fragment 'Catalog entry' front-loads a somewhat vague label rather than the primary action, but the overall structure is efficient and readable.

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 tool with no output schema, the description covers the core action and scoping. Gaps remain around how seller SKU and marketplace are determined, what the returned list entries look like, and whether the tool is actually invocable from the current environment. It is close to sufficient but not fully complete.

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 zero schema parameters, the baseline is 4. The description adds domain scoping by stating the codes are 'for a seller SKU in a given marketplace,' which provides meaning beyond the empty schema. It does not fully clarify how those values are supplied since no parameters are declared, but it still gives useful semantic context.

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?

States a concrete operation: 'Returns a list of return reason codes for a seller SKU in a given marketplace.' The verb and result are clear and distinguish it from the sibling tools. The opening 'Catalog entry' and 'Runs in your Kuudo deployment, not here' add context but do not obscure the core purpose. It stops short of a 5 because it does not explicitly contrast with any alternative tool.

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 about when to use this tool versus alternatives. The only usage-related signal is 'Runs in your Kuudo deployment, not here,' which hints at remote execution but does not explain prerequisites, exclusions, or preferred alternatives. The agent is left to infer usage context from the tool name and description.

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