gmail_delete_smime

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

No annotations present, so description must cover side effects. It only says 'Delete' without disclosing irreversibility, required permissions, or that the smimeId must be obtained from other endpoints. Missing critical context.

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?

While very short, the description is overly terse and sacrifices useful information. It could include minimal context (e.g., 'permanently removes') without significant length increase.

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 no output schema, the description should hint at return behavior or side effects. It fails to mention that deletion is irreversible or that the user must have appropriate permissions. Not complete for a delete 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?

Input schema already describes both parameters (smimeId and sendAsEmail) with 100% coverage. Description adds no extra meaning or context, so baseline 3 is appropriate.

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?

Description states the action (Delete) and resource (S/MIME configuration), but is too brief to distinguish from many sibling delete tools (e.g., gmail_delete, gmail_delete_label). It lacks specificity about what an S/MIME configuration is.

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 (e.g., gmail_set_default_smime). Prerequisites (e.g., needing an existing S/MIME config) are not mentioned.

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