MerchantFulfillment_getShipment

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

No annotations are present, so the description carries the behavioral disclosure burden. It does convey a read-only intent with 'Returns' and mentions an unusual execution context ('Runs in your Kuudo deployment, not here'). However, it omits required inputs, authorization needs, and failure behavior, and the 'Catalog entry' phrasing is ambiguous.

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 very short, but the first sentence is vague and wastes the prime position on 'Catalog entry' rather than the actual purpose. The useful functional statement comes only after a confusing environment note, so the structure is not ideal.

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?

There is no output schema, no parameter schema, and no annotation context. The description explains what the tool returns at a high level but not how the agent should identify the shipment, what inputs to provide, or what response shape to expect. An agent cannot reliably invoke this tool correctly based on this description alone.

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 with additionalProperties allowed, so there are zero documented parameters and nothing for the description to clarify beyond that. The description implies that an existing shipment must be identified, but does not name shipmentId. Per the 0-parameter baseline, the description is adequate.

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 verb and resource: 'Returns the shipment information for an existing shipment.' This clearly indicates a read-only lookup. However, it does not explicitly differentiate itself from sibling getShipment tools like ShippingLegacy_getShipment or FulfillmentInbound_getShipment, and the 'Catalog entry' opener adds confusion.

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 alternatives such as Shipping_getTracking, ShippingLegacy_getShipment, or FulfillmentInbound_getShipment. The phrase 'Runs in your Kuudo deployment, not here' hints that the tool may not be invocable in the current context, but it never states when to use or avoid it.

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