list_automation_enrollments

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

No annotations exist, so the description must fully convey behavioral traits. It merely states the action without disclosing read-only nature, pagination behavior, authentication needs, or error conditions. The presence of cursor and limit parameters is not explained.

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 sentence, making it concise but too minimal. It lacks structure and additional context. Given five parameters and no output schema, the description could benefit from more detail while remaining concise.

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?

The tool has multiple parameters, no output schema, and no annotations. The description only covers the basic purpose, leaving the agent uninformed about pagination, filtering by state, authentication override (apiKey), and return format. Significant gaps exist.

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 only 40%, and the description adds no parameter explanations. With low coverage, the description should compensate but fails to clarify the purpose of limit, state, cursor, or other parameters.

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') and the resource ('enrollments for an automation') with scope ('active and historical'). It effectively distinguishes the tool from sibling tools like list_automations and list_contacts.

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 explicit when-to-use or when-not-to-use guidance is provided. The description implies usage for retrieving enrollments, but does not mention alternatives or prerequisites, such as when to use this versus get_automation or other listing tools.

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