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

readOnlyHint=true already establishes the safety profile, so the bar is lower. The description adds real behavioral detail beyond annotations: result ordering, the exact reply envelope (offers, count, next_offset), and the underlying endpoint, making the read+pagination contract transparent. It does not mention auth scoping beyond the path template or rate limits.

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?

Three short sentences, no filler: what it lists first, pagination second, reply shape and endpoint last. Front-loaded with the action and result ordering.

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 8 optional params, no output schema, and no nested objects, the description covers the return envelope and the pagination loop, which is the main thing an agent needs that the schema cannot express. Minor gap: it doesn't frame what the date/search filters are for, though the schema documents each one.

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 100% and every parameter carries its own description, including the next_offset pagination hint, which the description merely echoes. Baseline 3 applies since the schema does the heavy lifting and the description adds no parameter detail beyond it (the seven filter/date params are untouched).

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?

Specific verb plus resource ('List the offers') with a parenthetical that disambiguates offers as product stock updates, and it names the ordering ('newest first') and returned fields. Among siblings this is clearly the read path counterpart to channable_update_stock, so an agent can select it 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 only usage instruction is the pagination loop ('pass next_offset as offset'), which is genuinely actionable. There is no statement of when to prefer this over channable_update_stock or other list tools, and no exclusions or prerequisites (e.g. project scope requirements).

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