gmail_mark_read

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

Annotations already establish that this is a non-read-only, idempotent, non-destructive operation. The description adds the key behavior that read=false causes unread, but it does not reveal any other side effects or prerequisites. No contradiction with annotations.

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?

Five short lines, no filler; the core capability appears in the first sentence, and the Args block is minimal and directly tied to the schema.

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?

For a simple two-parameter state-change tool, the description, together with the annotations and the existing output schema, provides enough information to make the call correctly. The only missing element is explicit selection guidance, but the operation is simple enough that this is a minor gap.

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 description coverage, the description fully compensates by explaining message_id as the target message and read as the state switch ('True marks it read, False marks it unread'), which is exactly the semantic information an agent needs beyond the raw types.

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 the exact operation with a verb ('Mark') and resource ('message'), and specifies the two possible outcomes ('read' or 'unread with read=false'). This is unambiguous and separates it from sibling tools like gmail_trash, gmail_archive, and gmail_modify_labels.

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 explicit guidance about when to choose this tool over alternatives or when not to use it. There are no excluded cases or pointers to sibling tools; the only implied context is the operation's own name and the read flag behavior.

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