batch-mark-as-unread

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

No annotations exist, so description carries the burden. It discloses the mutation action, return counts (success/failure), but does not cover idempotency, error details, or authorization. Adequate given the simple mutation.

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 well-structured sentences with front-loaded purpose, return info, and exclusions/prerequisites. No wasted words.

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 simple batch operation and presence of an output schema, the description covers usage, return, and exclusions. Missing are details on partial failures or idempotency, but the return count addresses basic completeness.

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 only parameter (ids) has 0% schema description coverage. The description repeats the min/max count from schema (1–100) and suggests sourcing from other tools, adding minimal semantic context beyond the schema pattern.

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 specifies the verb (mark), resource (messages), action (as unread), and scope (batch, 1–100 ids). It distinguishes from siblings by stating alternatives for single message or marking read.

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?

Explicit 'Use when' and 'Do not use when' sections, naming sibling tools mark-as-unread and batch-mark-as-read. Also provides a prerequisite step to get ids from search-messages or list-messages.

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