get_sms_thread

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that the output consists of chronological messages with direction, body, and timestamps, which is useful. It also reveals that the remote number must be in E.164 format. However, it does not mention pagination, limits, or edge cases, though for a read operation it covers the main behavioral traits.

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?

The description is concise and well-structured, with a one-sentence purpose, a one-sentence return summary, and two clearly formatted parameter explanations. It contains no unnecessary words or redundancy.

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?

The tool is a simple two-parameter read operation, and the description covers the core purpose, parameters with examples, and return format. The presence of an output schema means it does not need to explain the full return structure. It lacks details on pagination or date ranges, but for this simplicity and schema richness, it is adequately 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?

The input schema has zero description coverage, so the description's Args section fully compensates. It explains 'remote_number' as an external number in E.164 format with an example, and 'phone_number_id' as the user's own Commune phone number ID for the conversation, adding significant meaning beyond the bare parameter names.

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 clearly states that the tool retrieves all messages in an SMS thread with a specific number, using a specific verb and resource. It is distinct enough from siblings like 'send_sms' or 'list_sms_conversations', but it does not explicitly differentiate itself from 'get_thread_messages', which may serve a similar purpose for other thread types.

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 provides no guidance on when to use this tool versus alternatives such as 'list_sms_conversations' or 'search_sms'. It only describes what the tool does, with no implied or explicit usage context, leaving the agent to infer when it is the appropriate choice.

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