set_message_flags

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

With no annotations, the description carries the full behavioral burden. It implies a mutation but never says whether the operation is idempotent, what null flag values do (leave unchanged? clear?), what permissions are needed, or whether the change is reversible. Only the surface effect is disclosed.

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?

A single front-loaded sentence with zero filler; the core effect is stated before anything else.

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 4-parameter mutation tool with no annotations and 0% schema coverage, the description is too thin. Although an output schema exists (so return values needn't be explained), the missing uid/folder semantics and undefined null-flag behavior leave the agent unable to call it confidently.

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 coverage is 0%, so all four parameters lack documentation in structured fields. The description obliquely conveys the meaning of read and starred via 'read/unread' and 'starred/unstarred', but says nothing about uid, the folder parameter, or — critically — that null (the default) means the flag is untouched.

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 (Set) and resource (message read/starred flags), and enumerates the two flag axes precisely enough to distinguish it from mutation siblings like move_message, archive_message, and delete_message. It does not explicitly name a sibling it differs from, so it falls 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?

There is no when-to-use guidance, no prerequisites (e.g. that the message must be identified by uid within a folder), and no mention of alternatives such as get_message for reading flag state. The agent gets a capability but no routing context.

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