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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine beyond-schema context: results are ordered most-recent-activity-first and each conversation carries participants, assignee, and last-activity metadata. It stops short of describing pagination defaults or result volume behavior.

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 tightly packed sentences with zero filler: the ordering/scope clause comes first, then the return-shape note, then the REST mapping. Every clause carries information an agent can use.

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-only list tool with full schema coverage, the description supplies the missing pieces (sort order, returned per-item fields) and maps to the underlying endpoint. It would be complete at 5 if it noted pagination/nextPageToken behavior, since no output schema exists to convey that.

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 one of the 9 parameters is already documented with types and formats in the schema. The description only restates the filter categories (phone numbers, user, date ranges) without adding syntax, defaults, or interactions, so 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 conversations (threads)'), plus sort order and the filterable dimensions. The resource noun itself separates it from siblings like openphone_list_messages and openphone_list_calls, so an agent can route without opening any 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?

Usage context is only implied by the mention of optional filters ('optionally filtered by phone number(s), user, and created/updated date ranges'). There is no explicit statement of when to prefer this over sibling list tools and no exclusions or prerequisites, leaving routing guidance to inference.

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