ck_list_sequences

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention authentication requirements (beyond the implied api_key), rate limits, or the nature of the output (e.g., paginated list). The description adds no behavioral context beyond the basic operation.

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 extremely concise at one sentence, which is generally positive, but it sacrifices necessary detail. The key information is front-loaded ('List all email sequences'), but the lack of supplementary context reduces its effectiveness.

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 schema coverage (0%), missing annotations, and no output schema, the description is insufficiently complete. It does not describe the response format, any filtering options, or error states, leaving the agent with significant ambiguity about how to use the tool effectively.

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 0%, meaning the schema provides no documentation for the api_key parameter. The description does not explain what the api_key is or how it should be obtained, leaving the agent to infer its purpose from common conventions. For a single required parameter, this is a significant gap.

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 ('List all email sequences') and the resource ('in a ConvertKit account'), making the tool's purpose immediately understandable. However, it does not explicitly differentiate from sibling tools like ck_list_forms or ck_list_tags, which follow the same naming pattern.

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 provides no guidance on when to use this tool versus alternatives (e.g., ck_list_tags, ck_list_subscribers). It does not mention prerequisites, such as requiring an API key, nor does it suggest scenarios where listing sequences is appropriate.

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