Create domain filter

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

Annotations cover the safety profile: it is a non-read-only, non-destructive, non-idempotent, open-world operation. The description adds useful behavioral detail beyond that by saying invalid domains are skipped and returned in `rejected_domains`, and that attachment happens separately in the dashboard.

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?

Three short sentences, front-loaded with the core action and followed by the most important behavioral caveat and post-creation step. There is no wasted language.

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?

For a creation tool with no output schema and only 50% schema description coverage, the description should explain more about required fields and the return shape. It does provide the rejected-domain behavior, but omits meaningful details about naming, optional IP entries, and how the created filter is identified.

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 50%, and the description clarifies list_type values and invalid-domain handling for domains. However, it does not explain the required `name` parameter or the optional `ips` parameter, leaving clear gaps in parameter semantics.

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 states a specific verb and resource: creating a domain blacklist or whitelist filter. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as add_domains_to_filter or list_domain_filters.

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 only usage-related detail is that the filter must later be attached to an order in the dashboard. It does not explain when to create a new filter versus using add_domains_to_filter, nor does it mention prerequisites or exclusions.

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