get_unsubscribed_subscribers

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

The description mentions pagination but does not disclose additional behavioral traits such as default page size, maximum results, error handling for invalid list_ids, or rate limits. No annotations are provided to supplement this.

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 a single, front-loaded sentence that efficiently communicates the tool's purpose without unnecessary words or repetition.

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 straightforward paginated listing tool with well-documented parameters, the description covers the essential function. However, it could be improved by mentioning default pagination behavior or the format of the response (e.g., list of subscriber objects).

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?

Input schema has 100% description coverage, so the description adds no extra meaning beyond what the schema already provides. 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 clearly states the action ('Get'), the resource ('unsubscribed subscribers'), and the scope ('for a list'). It also mentions pagination, which distinguishes it from related tools like 'get_subscriber' or 'get_subscriber_history'.

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 implies usage for retrieving unsubscribed subscribers but does not explicitly state when to use this tool versus alternatives (e.g., 'get_active_subscribers', 'get_unconfirmed_subscribers'). No when-not or exclusion criteria are provided.

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