gmail_mark_thread_read

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

The description reveals that the tool works by removing the UNREAD label, which adds behavioral context beyond the bare action. However, with no annotations provided, it lacks other important traits (e.g., reversibility, authentication needs, or 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?

The description is a single, front-loaded sentence with no unnecessary words. Every word contributes to the purpose.

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 the low schema coverage (0%) and no annotations, the description is too brief. It does not explain the return value (output schema exists but is ignored) or provide sufficient context for the two parameters, leaving the agent underinformed.

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 description does not explain either parameter. The input schema has 0% description coverage, so the description should add meaning for 'thread_id' and 'user_id', but it fails to do so, leaving the agent without context on required identifiers.

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 clearly states it marks a Gmail thread as read by removing the UNREAD label. It uses a specific verb ('mark') and resource ('thread'), and distinguishes itself from sibling tools like gmail_archive_thread and gmail_mark_thread_done.

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 versus alternatives, such as archiving or marking done. It does not specify prerequisites, conditions, or exclusion cases.

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