ck_list_subscribers

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds little beyond restating that this lists subscribers for an account; it does not explain pagination despite a 'page' parameter, rate limits, auth requirements beyond the schema, or what the response contains.

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 with no filler and no structural ambiguity. Its brevity is appropriate in form, though the missing details are penalized under other dimensions.

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 six-parameter external API listing tool with no output schema, the description is too thin. It omits pagination behavior, filtering semantics, sorting behavior, and authentication context, leaving the agent to infer important call details from the schema alone.

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?

With six parameters and only 50% schema description coverage, the description needs to compensate by explaining filters and pagination, but it does not. It says nothing about 'from'/'to' date filtering, 'page', 'sort_field', 'sort_order', or the required api_secret.

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 states a specific verb and resource ('List all subscribers') and scopes it to a ConvertKit account. It is clearly distinguishable from write-oriented siblings like ck_add_subscriber and ck_tag_subscriber, though it does not explicitly name any alternatives.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no mention of related listing tools such as ck_list_forms or ck_list_tags. The listing purpose is implied by the name and sentence, but the description provides no usage decision support.

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