bulk_delete_by_subject

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

No annotations are provided, so the description carries full burden. While 'Delete' implies destruction, it lacks critical details: whether deletion is permanent or moves to trash, if the pattern matching supports wildcards/regex, case sensitivity, or performance implications of bulk operations.

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?

Extremely concise at 7 words with the action verb front-loaded. No filler words, though brevity comes at the cost of safety warnings and behavioral details that would be appropriate for a destructive bulk tool.

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 this is a destructive bulk operation with no annotations and no output schema, the description is dangerously minimal. It omits irreversibility warnings, confirmation requirements, and scope limitations (subfolders, date ranges) that would help an agent use this safely.

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 100%, establishing a baseline of 3. The description adds 'pattern' which hints at matching behavior (substring vs exact), but doesn't clarify pattern syntax, case sensitivity, or mailbox scoping beyond what the schema already documents.

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 verb (Delete), resource (emails), and scope (matching a subject pattern). It implicitly distinguishes from siblings like bulk_delete_by_sender by specifying 'subject pattern', though it doesn't explicitly compare against alternatives.

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 bulk_delete, bulk_delete_by_sender, or delete_older_than. No warnings about the destructive nature or prerequisites like confirming the mailbox selection.

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