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

readOnlyHint=true already establishes this as a safe read, so the description adds value by disclosing that all filters are exact matches (not fuzzy) and by explaining the source/source_id pairing rule, which is non-obvious behavior. It does not mention rate limits or result ordering, but the behavioral additions are genuinely useful.

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?

One dense paragraph that front-loads the returned fields and then the filtering semantics, with the endpoint at the end. Every clause carries information, though the enumerated field list makes it slightly long.

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, listing the returned fields (to, from, body, direction, source, status, credits, contact) is valuable and appropriate. Combined with the exact-match and source/source_id explanations, an agent has enough to call the tool correctly; only pagination behavior is left implicit.

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 high (88%) so most parameters are already documented, but the description adds meaning beyond the schema by clarifying that to/from can be used to pull a single contact's full history and that source_id is interpreted as a conversation id when source=InboxThread. That relational detail is not present in 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?

The description states a specific verb and resource ('List individual SMS/MMS messages sent and received by the brand') and enumerates the returned fields, making the scope clear. It implicitly separates itself from conversation-level siblings by stressing 'individual' messages and the InboxThread/conversation-id path, but it never names an alternative tool, so it falls short of full sibling differentiation.

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?

It gives concrete usage patterns: filters are exact matches, use to/from with a phone number to read one contact's history, or source=InboxThread with source_id set to a conversation id. That tells the agent how to shape calls for common intents, though it offers no explicit when-not-to-use guidance or named alternatives.

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