Archive a Gmail thread by removing its INBOX label to clear it from your inbox without deleting the conversation.
Archive a thread (removes the INBOX label).
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | No | ||
| thread_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| archived | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose all behavioral traits. It only mentions removing the INBOX label but omits other effects (e.g., whether it marks as read, permissions needed, or irreversibility).
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 a single sentence that is directly to the point, but it could be slightly expanded without losing conciseness (e.g., adding a note about thread scope).
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 the presence of an output schema, the description is minimally adequate. However, it lacks information on error states, required permissions, or side effects, leaving gaps for such a simple operation.
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 description coverage is 0%, and the description adds no explanation for the two parameters (user_id, thread_id) beyond their names. The agent must infer meaning from the context.
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) and the effect (removes INBOX label), making the purpose specific. However, it does not differentiate from the similar sibling 'gmail_archive_thread', which could cause confusion.
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 like gmail_archive_thread or gmail_inbox.mark_read. The agent receives no context about prerequisites or conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.