delete_email_config

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

With no annotations and no elaboration, the description does not disclose any behavioral aspects, such as whether deletion is permanent, idempotent, or what happens if the config does not exist.

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 extremely brief, which is concise, but it omits critical details that would make it more useful. It is structurally simple but not effectively informative.

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?

The description lacks context about error handling, return values, or side effects. Given the destructive nature of delete operations, more context is needed to use the tool 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?

The only parameter 'name' is present but lacks any description in the schema. The description does not clarify what the name refers to (e.g., a unique identifier, display name) or any constraints.

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 (delete) and the resource (email configuration), and the parameter name 'name' indicates the specific config to delete. It is distinct from sibling tools like add or update.

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, such as whether to use it before or after update_email_config, or any prerequisites like checking existence.

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