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 behavior beyond that: results are sorted by most-recent activity and each conversation carries participants, assignee, and last-activity metadata, plus the underlying REST endpoint. It does not explain pagination behavior, which is the one remaining gap.

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 compact sentences front-load the resource, ordering, and filters, followed by a short REST endpoint reference. No filler, though the endpoint line is marginally redundant for an agent that never calls the raw API.

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 9-parameter read tool with no output schema, the description covers resource, ordering, filter categories, and returned metadata, which is enough to invoke it correctly. Only pagination flow (pageToken/nextPageToken) is left entirely to the schema.

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 (userId, pageToken, maxResults, date bounds, phoneNumbers, excludeInactive) is already documented in the schema. The description restates the filter categories but adds no syntax, format, or defaulting detail beyond what the schema provides, 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?

The description gives a specific verb and resource ('List conversations (threads)'), states the ordering ('most-recent activity first'), and enumerates the filter dimensions. It cleanly separates this tool from siblings like openphone_list_messages and openphone_list_calls by naming the conversation/thread resource.

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 tells the agent which filters are available (phone numbers, user, created/updated ranges), which implies when the tool is useful, but it never states when to prefer this over a sibling such as list_messages or list_calls, nor any prerequisites. Usage is inferable rather than explicit.

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