list_exclusions_paged

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

Annotations already cover the read-only, idempotent, non-destructive safety profile, so the bar is lower. However, the description adds no behavioral context beyond restating the endpoint and operation; it does not disclose pagination defaults, page-size limits, or any response caveats.

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 brief and front-loaded with the summary and endpoint before the parameter list. It is not verbose, although the Args block mostly duplicates information already present in the input schema.

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?

Even with annotations and an output schema present, the description lacks practical invocation context: no explanation of what ImportListExclusion represents, no relationship to list_exclusions, and no pagination/sort behavior. An agent could infer the shape from the schema but would not be confident about the tool's semantics.

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 0%, so the description needed to explain the parameters, but it only repeats their names and labels them "Query parameter." It does not clarify sort_direction's object type, valid sort keys, default behavior when null, or page indexing.

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 a read operation and resource: "Read ImportListExclusion" plus the endpoint GET /api/v3/exclusions/paged. This is sufficient to understand what the tool does, but it does not explicitly differentiate itself from the sibling list_exclusions tool.

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 guidance is given about when to use this paged endpoint versus list_exclusions or any other alternative. The description only lists parameters and provides no context for choosing this tool over its siblings.

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