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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add real behavioral detail: it discloses pagination and explains non-obvious return semantics such as cap_period being counted in the workspace timezone and cap_used being null when no cap exists. That is genuine value beyond the annotations, though it says nothing about page-size limits or total-count metadata.

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?

Front-loaded with the verb and resource, then a single dense but purposeful sentence covering row contents. The cap field enumeration is long but each clause carries information an agent cannot get elsewhere given there is no output schema; no filler sentences.

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, describing the returned row fields is essential and the description does it thoroughly, including the null and fallback semantics of the cap fields. Combined with 83% parameter coverage in the schema, an agent has what it needs to call this correctly; only pagination metadata (total pages/count) is unaddressed.

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 83%, so the six inputs (page, search, status, country, network, per_page) are already documented with defaults and bounds. The description adds no meaning about the parameters themselves; its detail is spent on response fields, which is the correct baseline-3 outcome for a well-described 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?

"List offers (paginated)" states a specific verb and resource, and the following sentence enumerates the row fields (network, URL, payout, countries, cap fields), so the agent knows exactly what comes back. It does not explicitly contrast itself with sibling get_offer or create_offer, which keeps it short of a 5.

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 name and the presence of filter parameters; the description never says when to call this instead of get_offer (single offer lookup) or which filters to combine for common tasks. There are no exclusions or prerequisites stated, so an agent must infer the routing.

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