batch-unflag-messages

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

No annotations provided, so description carries full burden. It discloses return counts (how many unflagged and failed), batch size limit (1-100), and prerequisite ids. Does not mention idempotency or invalid id handling, but overall informative.

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 concise sentences, front-loaded with 'Use when'. Every sentence adds value: purpose, limits, return, alternatives, prerequisites. No redundancy.

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 batch tool with one parameter and output schema, description covers core usage, return value, prerequisites, and differentiation from siblings. Lacks error handling details but adequate for effective agent invocation.

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%, but description mentions 'removing flags from multiple messages (1–100 ids)' which explains the ids parameter implicitly. Also advises getting ids from other tools, adding context beyond schema pattern. However, does not elaborate on parameter format or validation.

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?

Description clearly states 'removing flags from multiple messages (1–100 ids) in one call.' Verb is specific (removing flags), resource is messages, scope is batch. Distinguishes from unflag-message and batch-flag-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?

Explicitly provides 'Use when' and 'Do not use when' conditions, including alternatives (unflag-message, batch-flag-messages) and prerequisite to get ids from search-messages or list-messages.

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