thunderbird_read_email

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

No annotations are provided, so the description carries the full disclosure burden, and it says only that one message is read. It does not describe the return shape, whether a message is marked read, required account/connection state, or error behavior for a missing id. For a no-annotation tool this is a notable gap.

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 text is short but defective: it terminates mid-sentence with 'returned: send...', so the most actionable part of the instruction (how to supply the id) is missing. Brevity comes from truncation rather than disciplined editing.

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?

With no annotations, no output schema, and an empty parameter schema, the description is the only source of behavioral and input information, and it is both truncated and inconsistent with the schema about the id argument. An agent lacks what it needs to invoke this tool reliably.

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 zero parameters, which normally yields a baseline of 4. Here, however, the description explicitly references an 'id' input that the schema does not contain, creating a mismatch that an agent must resolve by guessing. That reduces the value of the parameter information below the zero-parameter baseline.

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 verb and resource ('Reads one Thunderbird message') and even names the sibling tools that produce the id, so the core purpose is discernible. However, the sentence is cut off ('returned: send...'), and the schema declares zero properties, so the stated id input has no structured counterpart. An agent understands what the tool does but cannot reconcile it with the schema.

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 provides implied routing: obtain the message id from thunderbird_list_emails or thunderbird_search_emails before calling. That is genuine usage context, but there is no explicit when-to-use/when-not guidance and no distinction from other read tools such as thunderbird_search_emails or proton_read_email.

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