get_message

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

With no annotations, the description carries the burden of transparency. It correctly indicates a read operation ('Get') but does not disclose other behavioral traits such as required permissions, error cases, or any side effects. Minimal but not misleading.

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?

The description is very concise at 8 words, with no wasted text. It front-loads the key action. However, it could include slightly more structure or context (e.g., mentioning the optional parameter) without becoming verbose.

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?

The description covers the basic functionality but lacks information about return format, error handling, or result limits. Given the absence of an output schema and the presence of many sibling tools, a bit more detail would be beneficial, though it is minimally sufficient.

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 100% and both parameters are documented in the schema. The description only adds the vague phrase 'format options' without elaborating which parameter that corresponds to (likely includeBodyHtml). The schema itself provides sufficient detail, so the description adds little extra meaning.

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 clearly states the verb 'Get' and the resource 'message', specifying 'by ID' and mentioning 'format options'. It distinguishes itself from list-oriented siblings like 'list_messages' and other get tools for different resources, making the purpose unambiguous.

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?

The description implies use when you have a specific message ID but provides no explicit guidance on when to use this tool versus alternatives (e.g., list_messages, get_thread). No exclusions or comparative context are given.

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