list_offer_items

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

With no annotations provided, the description carries the full burden. It explicitly states 'Read-only' and 'with pagination', which are key behavioral traits. This is sufficient for a safe read operation, though it could mention the return format or authentication requirements.

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 two short sentences with no redundant information. It front-loads the core purpose and key behavioral note ('Read-only'), making it easy to parse quickly.

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 the lack of annotations, output schema, and parameter documentation, the description is too brief. It does not explain return values, error handling, authentication token usage, or pagination behavior beyond stating its existence.

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?

The schema has 3 parameters but 0% description coverage. The description only mentions 'pagination' without mapping to limit/offset. For an AI agent, this provides minimal guidance on how to use the parameters, despite defaults being present in 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 (offer items), and the scope (in the ExD catalog). It distinguishes this tool from siblings like get_offer_item (single item) and list_schema_descriptors (different resource) by specifying 'offer items'.

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 description mentions 'Read-only' and 'pagination', which provide basic usage context. However, it does not explicitly state when to use this tool over alternatives like get_offer_item or other list tools, nor does it provide exclusions or guidance on prerequisites.

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