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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the automatic sync cadence, what refresh actually does, and the required Cotlet API key with app access. It does not discuss pagination or empty-result behavior.

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?

Four tight sentences with the scoping statement front-loaded; each adds usable information (scope, sync/refresh semantics, ID contract, auth requirement). Slightly dense but no filler.

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, the description carries the return-value burden and does so enough: it explains what orders come back, their default unshipped state, and that IDs feed create_batch. Pagination behavior is absent but limit is documented in the schema, so nothing critical is missing for 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?

Schema coverage is 100%, so the baseline is 3. The description adds beyond the schema by clarifying that refresh requests new orders immediately and that source mirrors the Source filter in the Import grid, and it notes the returned IDs are the ones create_batch accepts.

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 (list) plus resource (import orders) and narrows the scope precisely: 'Unshipped orders from your connected store integrations, as in the Import grid.' This distinguishes it from sibling tools like pirate-ship_list_shipments or get_shipment, which deal with already-shipped data.

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?

Explains the default sync behavior and when to set refresh ('Orders sync on their own; refresh asks for new ones right away'), plus the source filter. It also connects the output to a downstream tool (create_batch). It stops short of naming an explicit alternative or when-not-to-use condition, so it is clear context rather than full routing guidance.

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