batch-mark-as-unread

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

No annotations provided, so description carries full burden. It discloses that it marks messages as unread and returns success/failure counts, but lacks details on side effects, reversibility, permissions, or rate limits. Adequate but incomplete.

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?

Efficiently structured with labeled sections: Use when, Returns, Do not use when, and prerequisite. Every sentence is valuable with no redundancy.

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?

For a simple batch mutation tool with one parameter and existing output schema, description covers usage, return, exclusions, and prerequisite. Lacks mentions of threading or access implications, but largely complete.

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 coverage 0% (description does not describe parameter format), but the schema provides a pattern for ids. Description adds context that ids come from search/list results. Baseline 3 due to low coverage, with partial compensation.

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?

Description clearly states the tool marks multiple messages (1-100) as unread in one call. It distinguishes from siblings like mark-as-unread (single) and batch-mark-as-read (read instead of unread).

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' with specific alternatives. Also provides prerequisite: get ids from search-messages or list-messages first.

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