list_sms_conversations

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

Describes return format (summaries) and optional filtering, but omits details like pagination behavior, ordering, or any side effects. No annotations provided to offload burden.

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 concise sentences for purpose/returns, then clearly formatted parameter list. No redundant information.

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?

Given simple tool with output schema, description adequately states return content and parameters. However, lacks mention of pagination continuation or ordering, leaving minor gaps.

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 has 0% description coverage; description fully compensates by explaining both parameters: phone_number_id as optional filter, limit with range and default. Adds clear value beyond the schema.

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?

Description clearly states it lists SMS conversation threads and specifies the returned summary content (remote number, last message snippet, message count). Differentiates from sibling email thread tools like list_threads by explicitly mentioning SMS.

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?

Implied usage: list all SMS conversations or filter by phone number. No explicit guidance on when to use this vs alternatives like search_sms or get_sms_thread.

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