kit_list_subscribers

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

With no annotations, the description carries full burden. It states the tool lists subscribers and returns paginated results, but lacks details on behavioral traits like rate limits, authentication requirements, or whether the operation is read-only. This is minimal but acceptable for a simple list 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 concise with only two sentences, front-loading the purpose and pagination behavior. Every word adds value without redundancy.

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 no output schema, the description should explain return structure. It mentions 'paginated results' but not fields of a subscriber. However, sibling tools like kit_get_subscriber may provide context. With 7 optional parameters and no required ones, the description is mostly complete but lacks return field details.

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%, so the schema already documents all parameters. The description adds no further meaning beyond what the schema provides, earning 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 uses a specific verb 'List' and resource 'subscribers', clearly defining the tool's function. It distinguishes from sibling tools like kit_get_subscriber (single subscriber) and kit_create_subscriber (create).

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 mentions optional filters and pagination but does not explicitly guide when to use this tool vs alternatives. For example, it does not say 'for listing all subscribers with filters, use this tool' vs 'for a single subscriber, use kit_get_subscriber'. The guidance is implied but not explicit.

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