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

readOnlyHint=true already establishes the safe-read profile. The description adds value by naming the return fields (text, direction, status, timestamps) and the backing REST call, but discloses nothing about pagination behavior, ordering, or result limits beyond what the schema shows.

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 front-loaded sentences with no filler; the core scope lands first and the return fields and endpoint follow. Efficient, though the endpoint reference is marginally redundant.

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 annotations covering the read-only safety profile, a fully documented schema, and no output schema to explain, the description is nearly sufficient. It only lacks pagination/ordering context for a list tool, which is a minor gap.

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 all seven parameters—including their formats (E.164, ISO-8601), constraints, and cross-tool hints—are already documented in the schema. The description adds no parameter-level detail, so the baseline 3 is correct.

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 (List) and resource (messages) scoped to a conversation between an OpenPhone number and participants. It is clearly distinguishable from openphone_get_message (single message) and openphone_list_conversations. The REST endpoint mapping reinforces the precise purpose.

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 when-to-use guidance relative to alternatives such as openphone_get_message for a single message or openphone_list_conversations. The description implies a listing scenario but never states when to prefer this tool or any prerequisites/exclusions.

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