List ClickBank orders

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

Annotations already declare readOnlyHint and openWorldHint, so the description does not need to restate safety. However, it adds little behavioral detail beyond the filtering scope and does not disclose pagination semantics, default date range, or how filters combine.

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: verb and object first, followed by the filter dimensions. Every word contributes, and it avoids duplicating schema details.

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?

For a 14-parameter tool with no output schema, the description plus input schema covers many mechanics such as page size, maxPages, and date format. Still, it lacks explicit statement of return shape and filter combination semantics, which are important 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?

With 50% schema coverage, the description helps by naming several undocumented filter parameters such as type, vendor, and email. But it omits role, item, lastName, and postalCode, and does not clarify whether filters are combined or mutually exclusive.

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 ('orders'), and the key filter dimensions ('date, type, vendor, affiliate, email, or tracking'). This distinguishes it from single-order or counting siblings, though it does not explicitly contrast with list_shippable_orders.

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?

No when-to-use guidance or alternative mention is present. The filter list implies a query use case, but an agent receives no help deciding between list_orders, count_orders, get_order, or list_shippable_orders.

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