MerchantFulfillment_getEligibleShipmentServices

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

With no annotations provided, the description must carry the behavioral disclosure burden. It helpfully discloses that this is a 'Catalog entry' and 'Runs in your Kuudo deployment, not here,' which signals non-executability in the current context. However, it does not clarify side effects, permissions, or what precisely the returned offers contain, leaving significant gaps.

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 front-loads the critical 'not here' caveat. The fragment 'Catalog entry.' is somewhat vague, but overall the text is efficiently sized.

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 the empty input schema and lack of an output schema, the description should provide enough context for correct invocation, but it does not. The 'not here' caveat is useful, yet the missing request-detail specification and lack of sibling differentiation leave the definition incomplete for an agent deciding whether and how to call it.

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, so there is little to document, but additionalProperties: true suggests arbitrary parameters are accepted. The description references 'specified shipment request details' without enumerating what those details are, so an agent cannot construct a valid request from the definition alone.

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: 'Returns a list of shipping service offers that satisfy the specified shipment request details.' This distinguishes it as a read/query operation within the MerchantFulfillment domain, though it does not explicitly differentiate it from sibling tools like Shipping_getRates or MerchantFulfillment_createShipment.

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 on when to use this tool versus alternatives. The phrase 'Runs in your Kuudo deployment, not here' hints that it may not be invocable in the current environment, but it does not name an alternative or provide a selection rule.

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