get_lists

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

No annotations are provided, so the description must disclose behavioral traits. It only describes the action without mentioning permissions, side effects, or return structure. As a read-only operation, it is safe, but the lack of any behavioral context (e.g., auth requirements, rate limits) reduces usefulness.

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, efficient sentence with no redundant words. It is front-loaded with the action and resource, making it easy to parse. Every word earns its place.

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 is simple (list all lists) and has no output schema, so the description is partially adequate. However, it omits details on return format, pagination, or the client context (e.g., which client's lists are returned). For a complete picture, additional behavioral information would be beneficial.

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 100% coverage with a description for the single parameter. However, the tool description does not add any meaning beyond the schema; it does not mention the parameter at all. Thus, it provides no additional value for parameter understanding.

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 verb 'List all' and the resource 'subscriber lists for the Campaign Monitor client', making the tool's purpose explicit. It distinguishes itself from sibling tools like get_list_details (singular) and get_lists_for_email (filtered), so an agent can select it appropriately.

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 implies usage for retrieving all lists, but does not explicitly state when to use this tool versus alternatives like get_lists_for_email or get_list_details. No guidance on prerequisites or context is provided.

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