archive_messages

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

Annotations already indicate mutating and non-idempotent behavior, but the description adds valuable context: moving archives invalidates the provided short IDs, and there is a limit of 25 per call. This goes beyond the annotations and helps the agent understand consequences of use.

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 very concise, with two sentences and a short Args section. Every sentence adds value: the action, the ID invalidation warning, re-query guidance, and parameter format. No unnecessary words or repetition.

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 single-parameter tool, the description covers the essential information: purpose, parameter format, constraints, and post-call behavior. The output schema is present (per context signals), so return values need not be explained. It's sufficiently complete for an agent to use correctly.

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?

The input schema only names 'message_ids' with no description, so the description carries the full burden. It explains the format (comma-separated short IDs) and the limit (max 25), which is essential for correct invocation. The description compensates well for the 0% schema coverage.

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 action: 'archive emails (move to Archive folder)'. It specifies the resource (emails) and destination (Archive folder), distinguishing it from similar tools like move_messages. The purpose is specific and unambiguous.

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?

The description provides clear context: use this tool to archive emails. It also includes a critical post-condition (IDs become invalid, re-run search_messages). However, it does not explicitly mention alternatives or when not to use this tool, so it lacks explicit exclusions.

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