mail_sync_status

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses that the tool returns three categories of info but doesn't describe what 'freshness' means operationally, whether the call is read-only, whether it triggers any sync behavior, or what the output schema looks like despite an output schema being present. For a status/read tool, the absence of an explicit 'this is a read-only status check' statement is a 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 description is a single, tightly-written sentence that enumerates exactly what the tool reports: freshness, cursor status, and local object counts. No wasted words, no redundancy with the schema, and it front-loads the purpose. Excellent conciseness for a status-reporting tool.

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?

An output schema exists, so return value details are partly covered by structured data. The tool is simple (one param, no nested objects), and the description's three enumerations capture the core value. However, given the ambiguity around 'freshness' and the lack of any guidance about cursor semantics or when counts might be empty, the description leaves the agent to infer important behavioral context that a richer description would clarify.

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 schema has 1 parameter (account_id) with 0% description coverage, so the description must compensate. While the description names three return categories, it doesn't clarify the semantics of the account_id parameter beyond what the schema provides (which is essentially just a string type named Account Id). However, with a single obvious parameter whose meaning is inferrable from the tool name and sibling tools, the low coverage poses less risk. The description adds marginally to parameter comprehension.

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 'Return freshness, cursor status, and local object counts' names a specific resource (sync state) with concrete return categories (freshness, cursor status, counts). It distinguishes itself from sibling tools like mail_sync_now / mail_sync_now_all which likely perform sync actions rather than report status. However, it doesn't explicitly differentiate from mail_sync_initial, and 'freshness' is slightly ambiguous without a definition of what qualifies as fresh.

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 given on when this tool should be used versus alternatives. There's no mention of when to call it (e.g., before queries to check data freshness, after initial sync). The tool name implies it reports status but the description never states a recommended use case or lists exclusions. Given the presence of many sync-related siblings, explicit usage direction would be valuable.

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