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

Annotations already declare the mutation profile (readOnly=false, destructive=false, non-idempotent), so the bar is lower. The description adds real behavioral context beyond that: the 50-member cap and the predicate-ownership rule governing whether add/remove is legal. It omits permission/reversibility details, keeping it out of 5 territory.

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 dense sentences, front-loaded with the operations and ending with the key constraint. Every clause carries meaning, though the phrasing is compressed enough to require a second read.

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?

An output schema exists, so return values need no explanation, and the description covers the critical set-vs-query distinction and the member cap. Given the complex nested query object and 5-way op enum, more op-specific guidance would help, but the core is complete enough to invoke correctly.

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 only 14%, so the schema documents almost none of the 7 parameters. The description partially compensates by mapping the op enum values to intents (create/create_query/update/add_members/remove_members) and by implying name/query in 'update list metadata/query', but it leaves most parameter semantics implicit.

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 names specific verbs and the resource (create set/query lead lists, update, add/remove members), so an agent immediately knows this edits lead lists. It does not explicitly differentiate itself from adjacent siblings like delete_lead_list or edit_leads, but the verb+resource pairing is unambiguous.

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?

It gives a clear conditional rule: query-list membership is predicate-owned, and explicit add/remove only works on an editable set list. That tells the agent when add_members/remove_members will succeed vs fail. It stops short of naming an alternative tool for the query-list case, so it earns a 4 rather than a 5.

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