flag_message

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context by explaining the exact underlying effect (setting/clearing the IMAP \Flagged flag) and the default behavior of the flagged argument.

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 opens with the core action and then lists parameters in a clean Args block. It is appropriately sized with no wasted sentences, though the two-part summary/args split is conventional rather than notably tight.

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?

With 4 parameters, no output schema, and annotations already covering the safety profile, the description provides what an agent needs to invoke it. The main gap is the absence of usage/routing guidance relative to sibling tools.

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 0%, so the description carries the full burden and does document all four parameters. It usefully clarifies that flagged=true applies the flag while false removes it (and notes the default), though 'uid: Message UID' adds little beyond the schema title.

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?

States a specific verb (flag/unflag) and resource (message), and clarifies the mechanism (setting or clearing the \Flagged flag). It does not explicitly name or differentiate from similar siblings like mark_read, so it falls just short of a 5.

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?

Usage is implied by the tool's action rather than stated. The mention of 'Account name from list_accounts' gives a mild routing hint to a sibling, but there is no explicit when-to-use or when-not-to-use guidance.

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