list_import_list_exclusions

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

With no annotations provided, the description carries the behavioral burden. It clearly indicates a read-only operation through 'List' and adds a meaningful behavioral guarantee: excluded series will never be re-added by import lists. Pagination behavior is left to the schema, which is acceptable for this low-risk operation.

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 well-structured sentence with the core action front-loaded and the key behavioral nuance appended. Every word earns its place with no filler.

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 only optional pagination parameters and no output schema, the description is nearly complete. It identifies the resource, the read-only nature, and the distinctive semantics. Pagination details are covered by the schema.

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%, with both 'page' and 'page_size' already documented. The description adds no parameter-level detail, so the baseline score of 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 uses a specific verb and resource: 'List series excluded from import lists'. The clarifying clause 'series that lists will never re-add' adds meaningful scope that distinguishes this from list_import_lists and the add/delete exclusion siblings.

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 this tool is for viewing exclusions, and the defined scope ('series that lists will never re-add') makes the use case obvious. It doesn't explicitly name alternatives or when-not-to-use conditions, but the context is clear enough for a simple read-only list tool.

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