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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context about payload content (line items) and cross-entity linkage, but says nothing about how many orders come back or whether the response is paginated — a notable gap for an unfiltered list call.

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?

One front-loaded sentence carrying the scope, payload contents and linkage, followed by a short endpoint reference. Compact and waste-free, though 'GET /orders.' adds little for an agent that already knows this is a read tool.

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 parameters, the description carries the burden of saying what comes back, and it does (orders with line items, keyed by order_id). The only missing piece an agent would want is expected result volume / pagination behavior.

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 tool takes zero parameters, so the schema has nothing to explain and the baseline of 4 applies. The description correctly implies no filtering or arguments are accepted.

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?

States a specific verb and resource ('List orders sent to shipcloud') and adds substantive scope detail: order data includes line items, is used by the Return Portal, and links to shipments via order_id. This distinguishes an order from a shipment or tracker among the many list_* siblings, though it never explicitly contrasts itself with shipcloud_get_order.

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?

Usage is only implied by the verb 'List' and the note that orders are linked to shipments by order_id, which hints that per-order detail belongs in shipcloud_get_order. There is no explicit when-to-use/when-not statement, and nothing about result size or pagination for a tool with zero filter parameters.

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