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

Adds real context beyond the annotations: 'One page' discloses the result is not auto-paginated, 'drafting does not send' forecloses the assumption that replies are dispatched, 'Dates use the account time zone' disambiguates timestamps, and the untrusted-content warning is a genuine safety instruction. Annotations already cover the read-only/destructive profile, so this is a solid supplementary layer.

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?

Five short sentences, front-loaded with the purpose before mechanics and warnings. Every clause carries information; nothing is padding.

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?

There is no output schema, so the description should hint at the returned message fields, but it only says 'One page' without describing pagination continuation (offset max is 9999) or result shape. It does cover intent, safety, and time zone, so it is usable, but an agent still cannot predict the response.

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 description coverage is 0% for all 7 parameters. The description only clarifies the time zone for startDate/endDate; limit, offset, search, origin, and destination get no explanation of what they filter on (e.g. origin vs destination as phone numbers). The schema enforces types and ranges but conveys no semantics, so the description leaves most parameters opaque.

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 verb and resource ('Read inbound messages') plus the intent (triage and draft replies) and the underlying endpoint GET /v2/sms-incoming. It never explicitly distinguishes itself from smsglobal_get_incoming_message (single message) or smsglobal_list_outgoing_messages, which would be the natural confusion points.

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?

Usage is implied rather than stated: 'triage and draft replies' suggests a review workflow and 'read-only' suggests this is safe to call freely. There is no explicit when/when-not guidance and no named alternative (e.g. use get_incoming_message for a single message).

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