conduyt_list_drip_enrollments

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

With no annotations, the description must carry the behavioral burden; 'List' reasonably implies a read-only operation and the mention of contact/campaign details gives some sense of the payload. It says nothing about pagination behavior, ordering, result caps, or auth requirements, which is a moderate gap for a paginated list endpoint.

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?

Two sentences, no waste, with the core action and returned data front-loaded and the filtering options summarized immediately after. Nothing here is redundant filler.

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 read-only, fully schema-documented list tool with no output schema, the description covers purpose, payload contents, and filterability, which is close to sufficient. Only pagination/ordering behavior is left implicit, and the schema covers the pagination parameters themselves.

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 page, limit, status enum, contactId and campaignId are all documented in the schema. The description's mention of campaign/contact/status filters mirrors that without adding format or semantics beyond it, so baseline 3 applies.

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?

States a specific verb and resource ('List drip campaign enrollments') and adds what the records carry (contact and campaign details). It does not explicitly distinguish itself from the many drip siblings (conduyt_list_drip_campaigns, conduyt_get_drip_campaign, batch_pause/resume/stop_enrollments), leaving the agent to infer which resource is being listed.

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?

'Filter by campaign, contact, or status' hints at how to narrow results, implying this is the browsing/read tool for enrollments. There is no explicit when-to-use vs. the batch mutation siblings (pause/resume/stop enrollments) or the campaign-level tools, and no stated prerequisites.

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