bulk_set_flags

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

Describes chunked execution, validation behavior, and return of count. No annotations exist, so description carries burden; it covers key behavioral aspects without contradictions.

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?

Very concise: three sentences plus bullet-style arg list. Every sentence adds value, 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?

Covers all parameters, behavior, and return value. No output schema exists; description explains return count. Could clarify flag format constraints, but references set_flags validation.

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 has 0% description coverage, but description explains all four parameters with examples (e.g., '["\Seen"]'). Compensates well for missing schema descriptions.

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?

Clearly states 'Set or clear IMAP flags on multiple messages in a single operation,' with a specific verb and resource. Distinguishes from set_flags by noting efficiency and batch processing.

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?

Explicitly compares to looping set_flags and mentions efficiency (~500 UIDs per chunk). Does not give exhaustive when-not-to-use, but provides clear context for batch flag operations.

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