email_manage_email

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

No annotations are provided, so the description carries full burden. It names the actions but does not disclose behavioral details such as whether 'archive' moves to a specific folder, whether 'star' is reversible, or whether actions are idempotent. The description is minimally transparent.

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 with no extraneous information. It is front-loaded with the action verb and clearly communicates the tool's main function without waste.

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 tool has 3 required parameters, no output schema, and no annotations, the description provides insufficient context. It omits any discussion of side effects, required permissions, return values, or interaction with other tools. For a multi-action tool, more detail would improve completeness.

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%, yet the description adds no parameter-level details beyond the schema's enum. It does not explain what accountId or messageId represent, nor does it clarify the effect of each action value (e.g., 'archive' vs 'read'). The description adds minimal semantic value.

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 verb 'Archive, mark read/unread, or star' and the resource 'an email'. It effectively distinguishes from sibling tools like email_delete_email (deletion) and email_send_email (sending) by specifying the exact actions this tool performs.

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 implies usage for managing email state (archive, read/unread, star) but provides no explicit guidance on when to use this tool versus siblings. For example, it does not differentiate from email_delete_email for removal or email_get_email for reading. No exclusions or prerequisites are mentioned.

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