set_group_card

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

No annotations are provided, so the description carries the full disclosure burden. It does note that an empty card string clears the card, which is useful, but it says nothing about the mutation's permission requirements (typically admin/owner), failure modes (target not in group), or reversibility.

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 short, front-loads the purpose, and the parameter lines are compact. The :param block is largely redundant with the schema, but it costs little and does not obscure the primary statement.

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 three-parameter mutation tool with no annotations and no output schema, the description covers what each parameter means and one edge case (clearing), which is enough to invoke it. It falls short on the operational context an agent would want — required permissions and behavior when the target is not a group member.

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 100%, so group_id, user_id, and card are already fully documented in the schema. The description restates the same three meanings plus the empty-string semantics, adding no syntax or format detail beyond what the schema provides; baseline 3 is appropriate.

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: modify a group member's group card/nickname, and even names the underlying OneBot 11 action (set_group_card). It does not differentiate from near-siblings such as set_group_special_title, set_group_name, or set_friend_remark, which an agent could plausibly confuse it with.

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 when-to-use guidance, no mention of prerequisites (e.g., bot admin rights, target must be a group member), and no reference to alternative sibling tools for related profile edits. The agent must infer the appropriate context entirely.

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