tag_users

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

Annotations already indicate this is a mutating, non-idempotent, non-destructive operation. The description adds the specific behavioral scope that it is a bulk addition of tags to users, but provides no further details such as whether existing tags are preserved, error behavior, or side effects, which is acceptable given the lightweight operation and existing 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, front-loaded, concise sentence with no wasted words. It communicates the core operation effectively for such a simple tool.

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 has low complexity, an output schema, and useful annotations, so the description does not need to explain return values. However, it omits practical invocation details like valid tag_id requirements, openid_list length constraints, and whether the operation is partially applied on failure, leaving notable gaps for an agent that needs robust usage guidance.

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?

With 0% schema description coverage, the description needed to compensate by explaining tag_id and openid_list semantics. It only vaguely maps '标签' to the tag and '用户' to the users, but does not clarify the meaning of tag_id, the format or limits of openid_list, or the relationship between them.

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 '批量为用户添加标签' clearly states the operation: batch-add tags to users. It uses a specific verb and resource, and is easily distinguished from the sibling untag_users, which covers the opposite operation.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention untag_users, list_tags, or constraints such as requiring an existing tag_id. Usage is only implied by the verb '添加'.

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