List shippable ClickBank orders

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds domain scope and filter axes but does not disclose behaviors such as pagination, default date windows, or receipt/date interactions beyond what the schema already documents.

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 a single front-loaded sentence with no filler. It states the action, resource, and key filter dimensions in concise order.

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 seven optional parameters and no output schema, the description is economical but leaves response shape and pagination behavior to inference. It also does not clarify the relationship to sibling count/list tools, so an agent may need to rely on assumptions or the schema to fully anticipate the call.

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 description coverage is 86%, and the schema already documents days, page, date format, receipt override, and maxPages. The description's high-level grouping into status, date range, and receipt provides a useful summary but adds no new semantic detail beyond the schema.

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 clearly states the action ('List'), the resource ('physical-goods orders' / ClickBank shippable orders), and the main filtering dimensions ('shipped status, date range, or receipt'). This makes it distinguishable from siblings like list_orders or get_order even without opening the schema.

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 phrase 'physical-goods orders' implies the intended scope and the filter dimensions signal common use cases. However, it does not name alternatives or state when to prefer this over list_orders or count_shippable_orders, so usage guidance remains mostly implicit.

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