add_domain_blacklist

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

With no annotations provided, the description must disclose behavior, but it only states the action of adding. It doesn't mention side effects, required domain_groups, scheduling parameters (weekdays/time_range), or whether it replaces existing entries. This is essentially a restatement of the tool name.

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 short phrase that is under-specified. It does not waste words, but it also fails to provide necessary information, making it more of a placeholder than a concise, informative 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?

Given 5 parameters (1 required), no annotation context, and an output schema not shown, the description is severely incomplete. It provides almost no guidance for correct usage, leaving the agent to guess parameter meanings and behavior.

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 0%. The description does not explain any of the 5 parameters, including the required domain_groups. There is no semantics added beyond property names and defaults, so the agent cannot understand how to properly invoke the tool.

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 '添加禁止娱乐网站' translates to 'Add prohibited entertainment website', which conveys adding a blacklist entry for entertainment sites. However, it doesn't explicitly mention 'domain blacklist' or domain_groups, and could be confused with the sibling add_url_blacklist. It's specific enough to indicate an add operation on a blacklist for entertainment websites, but lacks precision.

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 given on when to use this tool versus alternatives like add_url_blacklist or list_domain_blacklist. The description provides no context for selection or exclusions.

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