zernio_list_sequences

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

No annotations are supplied, so the description must cover behavioral traits. It states the tool 'lists all message sequences', implying a read-only, non-destructive operation. However, it does not disclose if it returns all sequences across accounts or only those visible to the user, nor does it mention the optional accountId filter. Basic behavior is clear but lacks depth.

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, well-structured sentence that conveys the core purpose without any wasted words. It is front-loaded and easy to parse.

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 list tool with one optional filter parameter and no output schema, the description is nearly complete. It could be improved by mentioning that the list can be filtered by account and by distinguishing from similar list tools. However, the current description is sufficient for basic usage.

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 has one optional parameter 'accountId' with a description 'Filter by account ID'. Schema description coverage is 100%. The tool description adds no extra meaning beyond what the schema already provides; it does not mention the filtering capability or explain when to use it. Baseline score is 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 clearly states the tool lists 'all message sequences (drip campaigns)' for automated follow-up messaging. The verb 'list' and resource 'message sequences' are specific, and the alias 'drip campaigns' aids understanding. This distinguishes it from siblings like zernio_get_sequence (singular) or zernio_list_sequence_enrollments (enrollments).

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 guidance is provided on when to use this tool versus alternatives such as zernio_get_sequence (for a single sequence) or zernio_list_sequence_enrollments. There is no mention of when not to use it or any prerequisites. The description lacks context about typical use cases or constraints.

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