Set flags

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

No annotations are provided, so the description must fully disclose behavioral traits. It does not mention side effects (e.g., whether the operation is reversible), authentication needs, rate limits, or any constraints. This is an insufficient disclosure for a mutation tool.

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?

The description is a single, succinct sentence that conveys the core function without any extraneous words. It is well-structured and immediately understandable.

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 lack of an output schema, annotations, and only partial parameter descriptions, the description is too sparse. It does not explain return values, error handling, prerequisites, or the effect of not supplying optional parameters. A mutation tool like this requires more context for safe and correct invocation.

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 description coverage is 50% (the boolean parameters seen and flagged have descriptions, but mailbox and uid do not). The description repeats the boolean usage without adding new information. It does not explain the mailbox and uid parameters, failing to compensate for the schema gaps.

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 tool's purpose: marking a message read/unread and/or flagged/unflagged. It uses specific verbs (mark) and resources (message) and effectively distinguishes from sibling tools like archive_message or delete_message.

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?

The description implies usage for toggling read/flag status but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like using archive_message for moving messages. It is minimally adequate.

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