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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's job is to add behavior. It does: default page size, 'newest last' ordering, the full set of returned fields, and the cursor-chaining rule for older pages. Return shape matters here because there is no output schema, and ordering/pagination disclosure is exactly the kind of context annotations cannot carry.

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 sentences, front-loaded with the resource and scope, then the pagination rule. Dense but every clause carries information; the long field enumeration is the only mild readability cost.

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 usefully names the payload fields, ordering, default page size and how to page backwards, which is what an agent needs to call and continue correctly. Only the absence of explicit sibling routing keeps it short of complete.

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%, so the schema already documents conversation_id, message_count (1-100, default 20) and the before cursor semantics. The description largely restates those facts rather than adding new meaning beyond the schema. Baseline 3 is appropriate.

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 resource and scope: 'One conversation with its most recent messages (default 20, newest last)' and enumerates the returned fields (body, from/to, direction, status, errors, media). This implicitly separates it from superphone_list_conversations (many conversations) and superphone_get_message (a single message), though neither sibling is named.

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?

Offers concrete operating guidance for pagination: 'To read older messages pass `before` = the previous reply's previous_cursor.' However, it never says when to reach for this tool versus superphone_get_message or superphone_list_conversations, so the selection guidance is only implied.

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