stalwart_get_queue_message

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

With no annotations, the description discloses key behavioral traits: it returns full detail including parsed headers and raw RFC 5322 message. It does not explicitly state it is read-only, but the verb 'get' and the return description imply safety. It could benefit from stating 'this is a read-only operation', but it provides meaningful context beyond the schema.

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 only two sentences, front-loaded with the main purpose, and includes a concise parameter explanation. No fluff or redundancy.

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 get tool with one parameter and an output schema, the description provides sufficient context: what it does, what the output contains, and how to obtain the required input. It is fully adequate for an agent to select and invoke the tool correctly.

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 has no parameter descriptions (0% coverage), but the description includes an Args section explaining that message_id is the queued message id from stalwart_list_queue. This adds crucial semantic meaning, though it does not specify the exact format or provide examples.

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 a specific verb ('Full detail of one queued message') and the resource (queued message). It distinguishes itself from sibling tools like stalwart_list_queue (listing) and stalwart_delete_queue_message (deletion) by focusing on retrieving full detail of a single message.

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?

It gives clear context for when to use the tool: to get full detail of a queued message, and explicitly mentions that message_id comes from stalwart_list_queue, implying a workflow. It does not explicitly mention when not to use it or list alternatives, but the parenthetical does guide usage.

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