list_incentives

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

The description discloses pagination behavior (page, page_size) and mentions the return format ('first page of incentives with envelope'). Without annotations, this provides adequate transparency for a read-only list tool.

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: two sentences and an example. Every part adds value, and the key information is front-loaded.

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 simple parameters and existence of an output schema, the description covers the core functionality. It could mention the envelope structure briefly, but the example implies it.

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 description explains the purpose of account_id via context ('for a dealer account') and provides an example with page. However, with 0% schema coverage, it does not fully document all parameters (e.g., page_size is only shown with default).

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 specifies the action (list), the resource (incentives, including rebates and finance offers), and the scope (for a dealer account). It distinguishes itself from sibling tools like get_incentive and search_incentives.

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 provides a concrete use case ('what rebates are available for dealer 1042 this month?') and an example with parameters. It implicitly shows when to use, though it does not explicitly state when not to use or mention alternatives.

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