remove_stop_list_email

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description merely restates the action without adding any extra behavioral context such as irreversibility, permission requirements, or side effects. No useful behavioral information is added beyond the structured annotations.

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, concise sentence that directly states the purpose. There is no unnecessary verbosity or repetition, making it highly efficient and front-loaded.

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 tool is simple, and the schema plus annotations cover the basic safety and parameter semantics. However, the description lacks any additional context about the effect of removal, return behavior, or when to use it, which would be beneficial given there is no output schema. The information is minimally sufficient but not rich.

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 description coverage is 100%, as each parameter (email, domain, dry_run, mail_from) has a description. The tool description itself does not explain the parameters, but the schema already provides adequate meaning, so the baseline score of 3 applies.

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 'Удалить email из стоп-листа' clearly specifies the action (remove) and the resource (email from stop-list). It distinguishes from sibling tools like add_stop_list_email and search_stop_list by the verb 'remove'.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or other context that would help an agent decide between this and similar tools like search_stop_list or add_stop_list_email.

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