Add Domain Blacklist

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

No annotations are provided, so the description carries the full behavioral burden, and it says nothing: not whether the entry takes effect immediately, whether it requires a target user/group context, whether existing entries are merged or overwritten, nor any permission requirement. For a mutating add operation this is a total gap.

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?

A single four-character phrase is not concise but under-specified; there is no structure, no front-loaded detail, and no information an agent can act on beyond the merest gesture at the resource type.

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 five-parameter write tool with zero annotation coverage and zero schema descriptions, the description supplies none of the scoping, sequencing, or parameter-format information needed to call it correctly. An output schema exists, so return values need not be described, but everything else is missing.

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% for five parameters, and the description adds no meaning for any of them. The format of domain_groups (the sole required field), the weekday bitmask syntax ('1234567'), the time_range format, and the roles of enabled/comment are all entirely undocumented.

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 Chinese phrase '添加禁止娱乐网站' ("add prohibited entertainment websites") conveys a verb and an object, so an agent can infer it creates an entry restricting entertainment sites. However, it never names the resource the tool actually manages (a domain blacklist entry / domain group) and gives no differentiation from the very similar sibling add_url_blacklist, so the purpose is only vaguely aligned with the tool 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?

There is no statement of when to use this tool, no prerequisites, and no mention of alternatives such as add_url_blacklist or list_domain_blacklist. The agent must guess from the name alone whether this is the right entry point for blocking domains.

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