list_pmp_deals

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

No annotations are provided, so the description should carry the full burden of behavioral disclosure. It only says 'List all PMP deals' without mentioning pagination behavior (despite limit/offset parameters), default limit, result structure, or whether it returns a summary or full objects. The read-only nature is implied but not explicit.

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 a single, concise sentence that front-loads the purpose. It contains no fluff and is appropriately brief for a simple list tool, though it is minimal enough that it misses opportunities to convey more useful context.

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?

The tool is a paginated list operation with two parameters and no output schema or annotations. The description is too sparse: it does not mention pagination, limit/offset usage, or that get_pmp_deal exists for fetching a specific deal. This leaves the agent without enough context to fully understand the tool's behavior.

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%, so the schema already documents limit and offset with descriptions. The tool description adds no additional meaning beyond what the schema provides, so the baseline 3 applies.

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') and the resource ('all PMP deals') with scope ('in your AdButler account'). This distinguishes it from sibling tools like get_pmp_deal, create_pmp_deal, update_pmp_deal, and delete_pmp_deal, which are all different operations.

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?

No usage guidance is provided. The description does not mention when to use this tool vs. alternatives like get_pmp_deal, nor does it clarify that this is for bulk listing while get_pmp_deal is for retrieving a single deal. There is no explicit when/when-not or alternative tool reference.

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