thunderbird_connect

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

With no annotations, the description carries full behavioral burden but only vaguely states that it reports send capability. It does not disclose side effects, authentication requirements, idempotency, or whether it modifies connection state—critical for a tool named 'connect'. The incomplete trailing colon further obscures behavior.

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 a single truncated fragment that fails to complete its thought. While short, it is under-specified rather than concise, and the trailing ellipsis suggests missing content that an agent would need.

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?

Given no annotations, no output schema, and a connection-oriented tool, the description is far too incomplete. It does not explain what 'connecting' entails, what state changes occur, or what the tool returns beyond a vague mention of send capability. It leaves major gaps for an agent to invoke 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 tool takes zero parameters, so the baseline is 4 per the rubric. The description does not need to add parameter semantics beyond what the empty schema already provides.

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 is a truncated sentence fragment ending with a colon and ellipsis, making its purpose unclear. It says the tool 'Reports... whether Local MCP can send' from each account, but the tool name 'thunderbird_connect' and sibling 'thunderbird_disconnect' imply it should establish a connection—creating a mismatch that would confuse an agent trying to distinguish it from siblings.

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 provided on when to use this tool, when not to, or what alternatives exist (e.g., thunderbird_list_accounts, thunderbird_disconnect, other *_connect tools). The description offers no context for invocation.

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