bulk_flag_by_sender

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it specifies the scope ('all emails'), it fails to mention whether the operation is idempotent, what happens to emails already in the target state, potential performance implications of bulk operations, or any permission requirements.

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, efficient sentence that front-loads the action. There is no redundant or wasted text; every word serves to define the tool's core function.

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 3-parameter tool without an output schema, the description covers the essential function but remains minimal. Given this is a bulk operation affecting potentially many emails, the lack of guidance on error handling, empty results, or confirmation mechanisms leaves it at minimum viability rather than comprehensive.

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?

With 100% schema description coverage, the baseline is 3. The description adds minimal semantic value beyond the schema, though it maps the 'flagged' boolean conceptually to the 'Flag or unflag' action. It does not elaborate on parameter formats, validation rules, or the default mailbox behavior beyond what the schema states.

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 provides a clear action ('Flag or unflag'), resource ('emails'), and scope ('all emails from a specific sender'). It implicitly distinguishes from sibling tools like 'flag_email' (single) and 'bulk_flag' (general criteria) by specifying 'by sender' in the name and 'specific sender' in the description, though it doesn't explicitly contrast with them.

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 offers no guidance on when to use this tool versus alternatives like 'bulk_flag' (which may filter by different criteria) or 'flag_email' (for single messages). There are no stated prerequisites, exclusions, or conditions that would help an agent select this over similar bulk operations.

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