exclusions_retrieve_a_list

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description reiterates 'Makes no changes' and includes a READ-ONLY icon, which adds minor emphasis but does not go beyond the annotations. No additional behaviors like pagination limits or rate limits are disclosed.

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 very concise (3 lines including icon and endpoint) with a clear front-loaded label 'READ-ONLY' and endpoint. Every element serves a purpose, but it could be slightly more informative without losing conciseness.

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?

Despite having 8 parameters and no output schema, the description does not explain the return format, pagination behavior, or typical use cases. It relies entirely on the schema, leaving gaps about what the response contains.

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 input schema has 100% description coverage for all 8 parameters, so the schema already documents parameter meaning. The description adds no extra parameter-specific context, resulting in a baseline score of 3.

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 explicitly states 'Retrieve exclusions list' and labels it as READ-ONLY, clearly indicating the action and resource. It distinguishes from sibling tools by naming the specific list type (exclusions), though it does not elaborate on what exclusions represent.

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 no guidance on when to use this tool versus alternatives. It simply repeats that it fetches data without changes, but fails to mention when it is appropriate or preferable to other list retrieval tools among the many siblings.

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