thunderbird_list_accounts

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

No annotations are provided, so the description carries the full burden. It does disclose a genuinely useful behavioral fact — the accounts come from the local Thunderbird profile on this computer, implying no network/auth round trip — and it partially enumerates the returned fields. It omits the connect prerequisite, error behavior when no profile exists, and whether the call has side effects.

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?

Single front-loaded sentence with no padding, which is the right shape for a zero-arg list tool. However it terminates mid-token ('type (imap, pop3 or...'), so the enumeration it sets up is never delivered — the structure is efficient but unfinished.

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 output schema, the description is the only place return values can be documented, and it does start that work (id, name, address, type). But the list is truncated and the description never says how to reach a callable state (thunderbird_connect) or what happens with multiple profiles, leaving meaningful gaps for an agent.

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 per the rubric the baseline is 4. The description cannot and need not add parameter meaning beyond the empty schema.

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?

States a specific verb and resource ('Lists the mail accounts of the Thunderbird profile') and scopes it to 'this computer', which separates it from remote-account siblings such as outlook_list_accounts or list_m365_accounts. It does not, however, explicitly name an alternative or state what makes Thunderbird accounts different, and the field enumeration is cut off mid-word.

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?

There is no statement of when to use this tool versus the many lookalikes in the sibling list (list_email_accounts, list_accounts, outlook_list_accounts, telegram_list_accounts, whatsapp_list_accounts). No prerequisites are given either — notably whether thunderbird_connect must run first.

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