Mark all matching read

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

Discloses key behaviors: reaches Spam/Trash via mailbox param, requires confirm for destructive/large batches, dryRun previews count, and max parameter limits. Since no annotations exist, description carries full burden and handles it well.

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?

Three sentences, no fluff, front-loaded with the primary action. Every sentence adds value.

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 6 parameters, no output schema, no annotations, the description covers all essentials: purpose, usage pattern, important parameters, and safety mechanisms. No gaps.

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?

Adds significant meaning beyond schema: explains query example, mailbox scope, dryRun/confirm semantics, and max parameter context. With 100% schema coverage baseline at 3, this description excels.

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 tool marks every message matching a query as read in one pass, with a concrete example. It distinguishes from siblings like mark_unread by specifying 'mark as read' and batch operation.

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?

Provides explicit guidance on using dryRun for preview and confirm for large batches. Could be improved by directly contrasting with single-message mark_read, but the intent is clear.

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