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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds genuinely useful behavior no annotation provides: results are a single page, and the agent must page through and disclose incomplete pagination before counting. That is meaningful operational context beyond the structured fields.

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?

Front-loaded with the core action and modes, then usage, then pagination caveat. Each sentence carries weight; the pagination warning is slightly repetitive but justified by the counting risk.

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?

With an output schema present, return values need no explanation, and the description covers scope, exclusions and pagination discipline. The main gap is that three parameters (limit, cursor, includeMembers) are undocumented by either schema or description.

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 coverage is 50% – ids, campaignId and workspaceId are documented in-schema while limit, cursor and includeMembers are not. The description adds some meaning (optional member inclusion, a 'bounded page', pagination) but does not explain limit/cursor defaults or ranges, so it only partially compensates.

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 ('Read lead lists'), plus the two retrieval modes (by ids or by campaign). It is clearly distinguishable from siblings like campaignstack_get_leads, campaignstack_edit_lead_list and campaignstack_delete_lead_list.

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?

Gives an explicit when-to-use cue ('when the user asks which lists exist or who is in them') and an explicit exclusion ('it does not add or remove members'). It stops short of naming the alternative tools, so it is strong but not a full routing instruction.

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