ExternalFulfillmentShipments_getShipments

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

No annotations are present, so the description carries the full burden of disclosure. It conveys a read-only list operation and a deployment-location detail, but it does not explain pagination, authentication, response contents, or what 'not here' actually means. The 'Catalog entry' label is undefined and adds confusion rather than transparency.

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, but not every sentence earns its place: 'Catalog entry' is unhelpful metadata, and 'Runs in your Kuudo deployment, not here' is cryptic. The core functional sentence is reasonably front-loaded and compact, but the surrounding filler reduces overall clarity.

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?

With no annotations and no output schema, the description is the sole source of context, yet it omits how to specify the status, what fields are returned, whether results are paginated, and what 'Kuudo deployment' means. For a list operation with an effectively empty schema, an agent cannot reliably construct a correct invocation.

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 declares zero properties, but the description says 'in the status you specify,' which implies a status filter without naming the parameter or accepted values. Because additionalProperties is true, an agent might try passing a status key, but nothing in the schema or description confirms how to do so. The description adds some meaning beyond the empty schema, but it leaves the agent guessing.

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 specific action ('Get a list of shipments') and resource ('shipments created for the seller'), and it mentions filtering by status. This clearly distinguishes it from the singular sibling ExternalFulfillmentShipments_getShipment. The phrase 'Catalog entry' is ambiguous and slightly detracts from the otherwise clear 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?

There is no guidance about when to use this tool versus the many shipment-related siblings, nor any mention of alternatives, prerequisites, or exclusions. The only contextual hint is that it 'Runs in your Kuudo deployment, not here,' which is a runtime-location note, not a usage guideline.

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