discord_get_message

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the action without detailing response format, error handling, permission requirements, rate limits, or side effects. Since this is a read operation with zero annotation coverage, significant behavioral context is missing.

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?

While the single sentence is technically concise, it is under-specified rather than effectively concise. It omits essential details about parameters and usage, so it fails the requirement that every sentence earns its place by providing valuable information. Terseness without substance scores low.

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 presence of an output schema reduces the need to describe return values, but the description remains incomplete. It does not explain prerequisites (e.g., needing channel_id and message_id), how this differs from similar message-fetching tools, or when to prefer it. The description is too sparse to enable correct selection and invocation.

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%, meaning the schema provides no parameter explanations. The description must compensate but does not—it never mentions channel_id, message_id, or guild_id, nor their roles. The phrase 'by ID' is too vague to clarify which IDs are needed or why guild_id is optional.

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 'Fetch a single message by ID' clearly states the specific verb (Fetch) and resource (a single message by ID). It distinguishes from sibling tools like discord_get_recent_messages, which fetch multiple messages, and discord_get_channel, which fetches a channel. The purpose is unambiguous and non-tautological.

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 given on when to use this tool versus alternatives such as discord_get_recent_messages or discord_search_members. There is no mention of context, exclusions, or alternative tools. The description is a bare statement with no usage direction.

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