listOffers

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It communicates a read/list operation but does not mention pagination defaults, ordering, whether 'all' is actually bounded by limit/offset, or the response shape. This is minimal and leaves important behavior implicit.

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 extremely concise with no filler, and the verb-resource pair is front-loaded. It is appropriately terse for a simple enumeration tool, though it sacrifices informative content for brevity.

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 simple tool with two optional parameters fully covered by the schema, this is minimally sufficient to make a basic call. However, with no output schema and no annotations, the agent must infer return format and pagination behavior, so the description is not fully complete on its own.

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?

Both parameters, limit and offset, are fully described in the input schema, giving 100% schema description coverage. The tool description adds no parameter-level detail beyond that, so it earns the baseline score for relying on 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 states a clear verb ('List') and resource ('offers'), so an agent can identify this as the enumeration endpoint for offers. It doesn't differentiate from sibling list tools like listProperties or listAudiences, and 'all' is slightly inconsistent with the pagination parameters, but the core purpose is unambiguous.

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?

There is no guidance about when to use this tool versus alternatives such as getOffer, listProperties, or listAudiences. No exclusions, prerequisites, or recommended conditions are provided, leaving the agent to infer usage from the tool name alone.

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