list_demand_endpoints

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'List all demand endpoints' and does not disclose pagination behavior, auth requirements, or any other traits. The word 'all' could be misleading given the presence of limit/offset parameters in the schema, and no additional context is added.

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?

One sentence, zero waste, and front-loaded with the action. Every word contributes to the purpose. This is an example of efficient, appropriately sized description.

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 list operation with two optional pagination parameters and no output schema, the description provides the essential purpose but lacks any information about return format, ordering, or the meaning of 'all' relative to pagination. Given the low complexity, this is a minimum viable description, but the lack of annotations and absence of return value details leave some gaps.

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 coverage is 100%, with limit and offset both having clear descriptions. The tool description does not add any parameter semantics beyond the schema, which is acceptable when coverage is high. The baseline of 3 applies because the schema does the heavy lifting.

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 uses a specific verb ('List') and clearly identifies the resource ('demand endpoints') and scope ('all... in your AdButler account'). This distinguishes it from sibling tools like get_demand_endpoint (single fetch) and create_demand_endpoint (mutation).

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 clearly implies use for enumerating all demand endpoints, but it does not explicitly mention alternatives or when not to use it. Sibling tool names like get_demand_endpoint suggest a single-item alternative, but no explicit comparison is provided. Context is clear but guidance is implied rather than stated.

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