Shipping_getShipmentDocuments

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It indicates a read operation ('Returns') and an unusual execution context ('Runs in your Kuudo deployment, not here'), but it does not disclose auth requirements, failure behavior, return format, or whether the tool is actually callable from this environment.

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 the functional action is not front-loaded; it appears only after 'Catalog entry' and 'Runs in your Kuudo deployment, not here.' The sentences are efficient, but the order and vague opening reduce structural quality.

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 output schema and no annotations, the description does not fully prepare an agent to invoke the tool correctly. It omits the structure of the returned documents and how the package/shipment reference should be supplied, and the environment caveat leaves it unclear whether invocation is even possible here.

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 are no parameter names or types for the description to explain; the baseline for a zero-parameter tool is 4. The phrase 'package in a shipment' adds domain context, though additionalProperties: true leaves some input ambiguity unresolved.

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 names a concrete action ('Returns') and a concrete resource ('shipping documents associated with a package in a shipment'), which is enough to distinguish it from sibling get-type tools like Shipping_getTracking. The opening 'Catalog entry' adds context but does not obscure the core function.

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?

The description gives no guidance on when to use this tool versus the many Shipping_* alternatives. It does not mention prerequisites, exclusions, or sibling tools, leaving the agent to infer usage only from the general action described.

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