set_message_flags

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

Description only restates the action without adding behavioral context beyond annotations. Annotations already indicate non-readonly and non-destructive, but no mention of side effects, permissions, or error cases.

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?

Single sentence, 16 words, front-loaded with key action and object. No filler or 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?

The tool is simple but the description lacks usage guidelines and behavioral depth. For a basic flag-setting tool, it covers the core purpose but misses context about when to use it.

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?

With 0% schema coverage, the description adds value by specifying 'RFC message-id' for the message_id parameter, but the boolean parameters are self-explanatory. It does not fully compensate for the lack of schema descriptions, but the tool is simple.

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 verb (set), resource (read and/or flagged status), and the identifier method (RFC message-id). It clearly distinguishes from siblings like bulk_mark_read which operates on multiple messages.

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?

No guidance on when to use this tool versus alternatives such as bulk_mark_read for bulk operations or read_email for just marking as read. No context for prerequisites or limitations.

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