Get message by message id

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the HTTP method and required OAuth scope, which is useful auth context, but does not describe response format, error behavior, or other runtime traits.

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 short and front-loaded with the core action, followed by the endpoint and scope. It is slightly redundant with the title, but the endpoint and scope information earns its place.

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 read-only fetch, the description covers the action, endpoint, and auth scope. However, because the input schema exposes no parameters, the description should more explicitly state that a message ID is required and how it is supplied; it also does not clarify the relationship with conversations_get_messages.

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 input schema is empty, so the description's mention of 'message id' and the endpoint path /conversations/messages/{id} is the only signal that an identifier is required. This adds essential meaning beyond the schema, though the exact argument name and type are not specified.

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 states a specific action and resource: 'Get message by message id' with a concrete GET endpoint and scope. This makes the tool's primary purpose clear and separates it from list-oriented siblings like conversations_get_messages, though it does not explicitly name any alternative tools.

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 phrase 'by message id' implies the tool should be used when a single message identifier is available, but there is no explicit guidance about when not to use it or which sibling to prefer. No exclusions or alternative tool references are provided.

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