domain_remove

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

The description adds no behavioral context beyond the endpoint. Annotations already indicate destructiveness (destructiveHint: true), but the description doesn't explain what is removed, whether it's reversible, or that dry_run can preview the request. The 'Python SDK parity' note is about implementation, not behavior.

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 short but under-specified. It lacks essential information, so it's not effective conciseness. The single phrase doesn't earn its place as a description.

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 is inadequate for a destructive tool. With no output schema and minimal annotations, the description should provide more context about the operation's effects and usage. It doesn't explain what blist domains are or the impact of removal.

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 description does not elaborate on the parameters. The schema defines domain (minLength 1) and dry_run (boolean with a Russian description), but the description adds no meaning. The domain parameter's purpose is not clarified beyond its name.

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 'POST /api/v2/blist/domains/remove' implies removing a domain from a blacklist based on the name and path, but it doesn't explicitly state the action or resource. It's not a tautology, but it's vague and doesn't clearly distinguish from sibling tools like update_blist or domain_add beyond the name.

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. There is no mention of scenarios, prerequisites, or relationships to sibling tools such as domain_add or domain_check_verification, leaving the agent without usage context.

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