sendcraft_list_subscribers

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states that the tool lists subscribers with status and tags. It does not mention pagination behavior, default limits, filtering semantics, or any access requirements, which are relevant for a listing tool.

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 short sentence that immediately conveys the core purpose with no filler words or redundant information. It is appropriately sized and front-loaded.

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?

Given the low complexity and 100% schema coverage, the description is passable but leaves gaps: there is no output schema, and pagination/response shape are not mentioned. It is sufficient for a basic tool but not comprehensively specified.

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 already provides descriptions for all four parameters, covering 100% of them, so the baseline is 3. The description adds minimal value beyond the schema, and 'tags' is not a parameter even though it is mentioned in the description.

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 'List subscribers/contacts' with a specific verb and resource, and it specifies the included fields (status and tags). This distinguishes it from sibling tools that send emails or manage campaigns, making its purpose unambiguous.

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 usage guidance is provided beyond the basic listing function. There are no when/when-not criteria, no mention of filters like status or list_id, and no reference to alternative tools like list_segments for more targeted subscriber views.

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