get_list_subscribers_tool

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower, yet the description still adds useful context: results are paginated one page at a time and include a total subscriber count. It stops short of stating ordering, page-size limits, or behavior beyond the last page.

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 tight sentences: the primary capability and returned fields come first, the prerequisite routing hint second. No filler, nothing redundant with structured fields.

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 and annotation only covering read-only safety, the description correctly spends its words on what is returned (name, email, status, total count) and on pagination, which is what an agent needs before calling. Missing only secondary details like sort order and page-boundary behavior.

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 defaults and constraints documented for `page`, `per_page`, and `list_id`, so the schema carries the parameter semantics. The description only hints at pagination ('one page at a time') and adds no format or range detail beyond the schema; baseline 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?

Specific verb+resource+scope: lists subscribers of one mailing list, one page at a time, and names the returned fields. It is distinguishable from most siblings, but it never distinguishes itself from the near-identically named sibling `list_subscribers`, leaving genuine ambiguity that only a schema comparison could resolve.

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?

Gives one concrete prerequisite: use `get_mailing_lists` to find list IDs, which is real routing help. However, it offers no when-not guidance and does not address how this differs from the sibling `list_subscribers`, which appears to do the same job.

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