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

readOnlyHint=true already tells the agent this is a safe read, and the description usefully adds that entries are opt-outs on call and text lists. However, the parenthetical '(type call or text)' is ambiguous — it implies type separation while the tool exposes no type parameter, leaving unclear whether both lists are merged in the response.

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?

One tight sentence with the resource and scope front-loaded and zero filler. Nothing is redundant with the title.

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?

For a two-param read-only list with annotations covering safety and schema covering pagination, the definition is nearly sufficient. The only real gap is whether the response returns both call and text opt-out lists combined or separately, which stays ambiguous.

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 100% with both parameters fully documented, including the next_start pagination hint, so the schema carries this dimension. The description adds nothing about limit or start, which is acceptable at this coverage level.

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 phone numbers on the account's do-not-contact lists') and clarifies what the entries represent ('these opted out'). It implicitly distinguishes itself from dialmycalls_list_contacts by scoping to opt-out lists, though it never names the sibling.

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 guidance on when to call this versus list_contacts or when to check these lists before send_call/send_text. The use case (compliance pre-check) is only hinted at by 'these opted out'; there are no exclusions or alternatives named.

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