batch-mark-as-unread

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

Discloses return values (counts of success/failure) and constraints (1-100 ids). No annotations exist, but description fills most gaps; however, does not mention idempotency 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?

Four concise sentences with clear sections. No wasted words, front-loaded with key information.

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 parameter set and presence of an output schema, the description covers usage, prerequisites, return values, and alternatives completely.

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?

Only one parameter 'ids'. Description clarifies it accepts 1-100 message IDs and suggests sourcing from search/list tools. With 0% schema coverage, this adds necessary context, though id format is left to 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 ('marking multiple messages as unread'), specifies the resource ('messages'), and distinguishes from siblings like 'mark-as-unread' and 'batch-mark-as-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 with alternatives for single message and read marking. Also advises to get IDs from other tools, providing clear context.

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