get_message

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

With no annotations, the description carries the burden of behavioral disclosure. It states the operation is a retrieval and promises 'message details', but it does not mention potential errors (e.g., invalid ID) or the exact structure of the return data. This is sufficient for a simple read but lacks depth.

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 concise, with a clear one-sentence overview followed by structured Args and Returns sections. Every line earns its place with no extraneous information.

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 one-param retrieval tool, the description covers the essential purpose and parameter. However, the return type is generically 'Dict[str, Any]' with no indication of expected fields, and error handling is omitted. Given no output schema, this leaves noticeable gaps in completeness.

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?

The schema has no parameter descriptions (0% coverage), so the description's line 'message_id: The ID of the message to retrieve' adds some meaning. However, it essentially restates the parameter name and type without providing format, origin, or examples, offering only marginal value over the schema.

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 'Retrieve a message by ID', using a specific verb and resource. It unambiguously distinguishes itself from siblings such as send_message and get_webhook_events, with no other get_message tool present.

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 a message_id is known and details are needed, but provides no explicit comparison to alternatives or exclusions. It falls short of offering clear guidance on when not to use this tool or directing users to other tools for different scenarios.

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