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

Annotations already cover readOnly/destructive/openWorld, so the description's added value is the untrusted-customer-content warning (a real prompt-injection caution) and the pagination note 'Returns one page unless stated otherwise'. It doesn't state default page size or ordering, which limits it to a 4.

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?

Three short sentences with the resource and scope front-loaded and no filler. The raw REST path sentence adds little beyond what the name and required dashboard_id already convey.

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, the description usefully enumerates returned fields (history, direction, contact numbers, delivery state) and warns about untrusted content, which is enough for correct invocation. Paging behavior (defaults, sort order, cursor vs. page) remains underspecified for a 5-parameter list endpoint.

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% across 5 parameters, so the description carries the burden. It clarifies that the date range is optional and UTC-based (useful given the pattern allows offsets), but says nothing about 'page'/'page_size' bounds or defaults, leaving two parameters undocumented anywhere.

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 (read) and resource (dashboard-wide message history) plus the returned attributes (direction, contact numbers, delivery state). The word 'dashboard-wide' implicitly separates it from textrequest_list_contact_messages, but the sibling is never named, so differentiation relies on inference.

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?

Scope language ('dashboard-wide') and the optional time range imply when to use it versus the per-contact message list, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer the routing rule from 'dashboard-wide'.

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