Reports whether Local MCP can send mail from each Thunderbird account on this computer, so you can identify usable sending accounts before composing a message.
Reports, per mail account of the Thunderbird profile on this computer, whether Local MCP can send from it:...
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.0.426Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it doesn't state whether this is a read-only probe, whether it triggers any account/auth checks, or whether it can have side effects. The one behavioral hint — it reports send capability — is useful but cut off by the ellipsis.
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?
Extremely short and truncated mid-sentence with an ellipsis, so it is under-specified rather than concise. The front-loaded clause is fine, but the definition is incomplete.
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?
No output schema and no annotations, so the description is the only source of truth, yet it stops before explaining what the report contains (per-account booleans, reasons, account identifiers). For a diagnostic/status tool this leaves a significant gap.
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 has zero parameters and an empty schema, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter detail is expected or needed.
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?
It has a specific verb ('Reports') and resource ('per mail account of the Thunderbird profile'), and it adds a useful filter concept (whether Local MCP can send from it). But the trailing ':' with an ellipsis means the actual list of reported fields is missing, leaving the exact output ambiguous and giving no explicit distinction from thunderbird_list_accounts.
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 when-to-use or when-not-to-use guidance. It doesn't say how this differs from sibling thunderbird_list_accounts or when an agent should call this vs. thunderbird_send_email to test sendability, so the choice is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.