get_message

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get a single message by ID' conveys only the basic read intent and says nothing about return format, errors, whether it marks the message as read, or any other behavioral trait.

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 a single sentence with no filler and addresses the core action immediately. It is concise and front-loaded, though it could include additional useful detail 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?

For a simple direct lookup requiring only chat_id and message_id, the description and schema together are minimally workable for an agent to invoke the tool. However, with no output schema, no annotations, and no mention of return values or edge cases, the description is not fully complete for callers who need to interpret the result.

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%, and the description only adds 'by ID' without explaining the roles of chat_id and message_id, their types, or how they interact. The parameters are relatively self-explanatory from their names, but the description does not provide the required compensation for the lack of schema descriptions.

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 names a specific verb and resource ('Get a single message by ID') and clearly indicates the tool retrieves one message rather than a list or search result. It distinguishes itself from broad read tools like search_messages and read_messages, though it does not explicitly contrast with siblings such as get_message_replies.

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 guidance is provided for when to use this tool versus alternatives like search_messages, get_message_replies, or read_messages. The description implies a direct lookup by ID, but it does not state when this is preferable or when another sibling should be selected.

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