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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful behavioral context beyond that: the endpoint is inferred rather than verified, results come back as a Feed, and there is a documented fallback tool when the inference is wrong. It still doesn't describe pagination traversal behavior explicitly.

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?

Three compact sentences: what it returns first, then the endpoint, then the caveat. No filler, and the most important scoping information (returned entity shape) leads.

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 no output schema, the description compensates by naming the returned fields (ListID/ListName) and the Feed format, and it documents every parameter via the schema. The inference caveat plus escape hatch closes the main reliability gap; only pagination semantics are left implicit.

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 every parameter (page, pagesize, takesize, params) is already documented in the schema. The description adds no syntax or merging detail beyond it, so the 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 saved contact lists'), then defines the domain term ('groups you can broadcast to') and the returned identity fields (ListID/ListName). It also pins the underlying operation (GET /v1/lists), so an agent can distinguish it from list_broadcasts or list_text_numbers without opening a schema.

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 conditional alternative: if the account/endpoint differs from the inferred model, use the textemall_request escape hatch. It does not explicitly rule out sibling list tools, but the routing guidance it does give is concrete and actionable.

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