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

Annotations already declare readOnlyHint=true and destructiveHint=false plus openWorldHint=true, so safety and reach are covered. The description adds little beyond that — it doesn't mention that results are paginated or that the list may be empty, though it does indicate ids are included in the response.

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?

Two short, front-loaded sentences with no filler; the resource and payload come first and the endpoint is appended as a compact reference. Nothing redundant beyond the REST path, which is arguably useful for debugging.

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?

With no output schema, the description carries more burden than it does — it names 'ids' but not the other fields returned (name, type, counts) or the pagination envelope shape, which matters for a list endpoint an agent will page through. Adequate but thin for a paginated listing tool.

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%: both limit and offset are fully documented, including the next_offset instruction. The description contributes no additional parameter guidance, which is acceptable at this coverage level.

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?

States a specific resource ('All blacklists (suppression lists) of the account') and what is returned ('with their ids'). The parenthetical clarifies the synonym, and the contrast with sibling sarbacane_list_blacklist_entries is inferable from 'blacklists' vs. entries, though not stated explicitly.

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?

Usage is only implied by the resource name; there is no statement of when to prefer this over sarbacane_list_blacklist_entries (to inspect the members of a blacklist) or any prerequisites. An agent must infer the routing from the sibling names alone.

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