mark_flagged

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

No annotations are provided, so the description must fully disclose behavior. It indicates a write operation via IMAP but does not describe error conditions (e.g., missing email), side effects, or whether the operation is reversible. This minimal disclosure is insufficient for safe invocation.

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 short (one sentence), which is concise but not structured effectively. It front-loads the core action but omits essential details that could be added without verbosity.

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 tool with 3 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return values, error handling, or confirm the effect on the email's flagged state. Sibling tools like bulk_mark_flagged suggest batch operations exist, but no comparison is given.

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%, and the description adds no meaning to any parameter. For instance, the 'flagged' boolean parameter is not explained (true=star, false=unstar), nor is the format of 'folder' or 'email_id' given. The description fails to compensate for the lack of schema descriptions.

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 (star/unstar) and resource (email) via the \Flagged IMAP flag, distinguishing it from flags like \Answered or \Read used by sibling tools. However, it does not explicitly say that the action toggles based on the boolean flag.

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 is provided on when to use this tool versus alternatives like bulk_mark_flagged (for multiple emails) or set_flags (for arbitrary flags). No prerequisites or context for when to star vs unstar are given.

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