Get Message

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

Discloses important behaviors: body can be large, options to manage size (truncation, preview, strip_html). Without annotations, this is valuable context.

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?

Very concise, well-structured with bullet-style options. Every sentence adds value without 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?

Provides enough context (body options, HTML handling) for an agent to select and invoke correctly. No output schema needed given clarity of description.

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?

Adds meaning beyond the 100% covered schema: clarifies body_format values (e.g., preview returns 500 chars), and explains strip_html effect (converts HTML to plain text).

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?

Describes precisely 'Gets a single message by ID with full body content', clearly distinguishing it from sibling tools like list_conversations or send_message.

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?

Provides detailed guidance on body format options (full, truncated, preview) and when to use each, but lacks explicit when-not-to-use or alternative tools.

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