FulfillmentOutbound_listAllFulfillmentOrders

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

With no annotations, the description carries the transparency burden; it does disclose that this is a read/list-like operation, the date-time filter, and nextToken pagination. It does not disclose output structure, ordering, which order statuses are included, or any auth/rate-limit implications, leaving behavioral detail incomplete.

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 appropriately short and the core return behavior is front-loaded. The opening fragments 'Catalog entry. Runs in your Kuudo deployment, not here.' are slightly redundant and could be compressed, but there is no wasted explanatory filler.

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 output schema and no annotations, the definition omits important details for reliable selection and invocation: exact parameter names, return value structure, and relationship to sibling tools. The 'runs in your Kuudo deployment' note provides some execution context, but the entry remains too thin for an agent to call it correctly.

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 schema has zero declared properties but allows additionalProperties, so the description is the only source of parameter meaning; it correctly identifies the date-time filter and nextToken. However, it never names the actual query parameter(s) or their formats, so an agent still cannot construct the invocation reliably.

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 states the action ('Returns a list of fulfillment orders') and the resource, plus the key filtering semantics by date-time or nextToken. It is distinguishable from single-order tools like getFulfillmentOrder, though it does not explicitly name sibling alternatives and the 'Catalog entry' opener 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?

It provides useful context that the tool runs in the Kuudo deployment, not the current environment, and implies the main use case is listing orders fulfilled after a date-time. However, it does not explain when to choose this tool over related fulfillment-outbound operations or how pagination via nextToken should be handled.

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