bulk_mark_read

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

With no annotations provided, the description carries full burden but omits critical safety context: it doesn't warn that this mutates email state, affects potentially thousands of emails if unfiltered, or mention that 'bulk_mark_unread' can reverse it. For a bulk write operation, this lack of behavioral disclosure is a significant 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?

Single sentence, front-loaded with the primary action ('Mark all emails as read'), followed by the conditional scope. No redundancy or filler. Efficient length for the complexity level.

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?

Adequate for a two-parameter tool with complete schema documentation, but falls short for a bulk mutation operation. Missing: return value description, safety warnings about unfiltered usage, and reversibility notes. However, given the simple parameter structure and lack of output schema, it meets minimum viability.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds conceptual framing ('optionally filtered by sender') that aligns with the schema parameters, but doesn't provide syntax examples, format constraints, or semantic relationships beyond what's already in the 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?

The description clearly states the action ('Mark... as read') and resource ('emails'), using 'all' to indicate bulk scope. The phrase 'optionally filtered by sender' distinguishes it from date-based bulk variants like 'mark_older_than_read' and implies the difference from single-email 'mark_as_read', though it doesn't explicitly name siblings.

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 explicit guidance on when to use this versus 'mark_as_read' (single email) or 'mark_older_than_read' (date-based). No warning about the scope of 'all emails' or prerequisites. The agent must infer usage solely from the parameter descriptions.

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