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

With no annotations, the description carries the full burden: it does not confirm this is a safe read-only operation, does not say whether reading marks messages as read/consumed, does not describe ordering (newest-first?) or pagination, and does not mention rate limits or auth requirements beyond the schema's api_key field.

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?

A single well-formed sentence with no filler, and the core action is front-loaded. Its brevity is efficient, though it borders on under-specification rather than tight writing.

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?

For a three-parameter read tool with no annotations and no output schema, the description leaves too much open: the return shape (message body, sender, timestamps), the meaning of limit, and whether results are paginated are all unaddressed.

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 only 33% (only api_key documented), so the description must compensate and largely fails. 'One of your numbers' weakly maps to number_id, and 'recent' hints at limit, but neither the default/maximum for limit nor the expected number_id format is explained.

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 concrete verb and resource ('Read recent text messages') plus scope ('received on one of your numbers'), which clearly separates it from call-oriented and account-management siblings. It stops short of naming any sibling or clarifying whether 'read' returns content versus message metadata.

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 statement of when to use this versus alternatives, no mention that a number_id must be obtained from list_phone_numbers first, and no guidance on inbound-only vs outbound messages. The only usage signal is implied by 'received'.

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