mail_status

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value by disclosing the contents of the status payload (index progress, read-only mode, sending state, attention hints). What it does not say is whether the status is expensive to compute or whether counts are exact or approximate.

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?

A single front-loaded sentence that opens with the subject (Timbre's state) and then enumerates facets. The list phrasing is dense but every item names a distinct piece of state, so nothing reads as filler.

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 zero parameters, an output schema that documents the return shape, and annotations covering the safety profile, the description only needs to say what state exists, which it does. The remaining gap is the absence of explicit invocation guidance relative to the 16 sibling tools.

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 description carries no parameter burden and the baseline applies; the schema is empty and fully consistent with a no-argument status read.

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 names the resource (Timbre's state) and enumerates the specific facets reported: mail store, message counts, full-text index progress, settings, and attention hints. That is enough for an agent to tell it apart from the operational siblings such as list_mailboxes or search_mail, though it never states an explicit verb like 'get' or 'report'.

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?

Usage is only implied: the mention of 'settings (read-only mode, sending)' and 'hints when something needs the user's attention' suggests calling it before write operations or when diagnosing problems, but there is no explicit when-to-use statement and no named alternative among the 16 siblings.

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