bulk_mark_flagged

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

With no annotations, the description must carry behavioral disclosure. It only implies a set operation via 'Star or unstar' but does not explain whether it is a toggle, idempotent, or the impact on other settings. No mention of permissions or limits.

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 one short sentence, but it lacks details that would make it more useful. It is not concise in the sense of efficient communication; it is overly terse.

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 three parameters, zero schema coverage, and no output schema, the description is insufficient. It does not explain the required 'folder' parameter, the format of 'email_ids', or the effect of the 'flagged' boolean.

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 the description must add parameter meaning. It mentions none of the three parameters (folder, email_ids, flagged), leaving their purpose and format entirely unexplained.

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 stars or unstars multiple emails using the 'Flagged' flag. It distinguishes from siblings like 'mark_flagged' (single email) and 'bulk_set_flags' (general flag setting) by specifying the flag type, though explicit differentiation would be stronger.

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 guidance on when to use this tool versus alternatives such as 'mark_flagged' for single emails or 'bulk_set_flags' for other flags. No mention of prerequisites or context.

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