batch-flag-messages

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

Discloses return structure (counts of flagged/failed) and a critical behavioral note: IMAP-routed IDs can be flagged but colors are not applied (IMAP flags are colorless). With no annotations, this provides essential context.

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?

Three sentences with front-loaded purpose, then return info, then exclusions. No unnecessary words; every sentence adds value.

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 usage, parameters, behavior, and prerequisites. Lacks error handling or authentication details, but sufficient for a batch flagging tool with output schema.

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?

Adds context beyond schema: explains the color enum list, the 'grey' alias, and the IMAP color limitation. Also mentions the return counts. Schema coverage is 50%, and this compensates well.

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 it flags multiple messages (1-100 IDs) with optional color. Distinguishes from siblings by explicitly excluding single flagging (flag-message) and unflagging (batch-unflag-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?

Provides explicit 'Use when' and 'Do not use when' sections with alternative tool names. Also advises to 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.