群打卡

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

Annotations already indicate a non-read-only, non-idempotent action; the description adds the card-form detail. However, it does not clarify whether a visible message is sent, whether repeated calls create repeated check-ins, or whether rate limits or permissions apply.

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 one short sentence with no filler and states the action directly. It is efficient, though it could earn a higher score by embedding usage context without adding length.

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 simple one-parameter tool with annotations and full schema coverage, the description is minimally acceptable. Still, the exact visible effect and the boundary between this tool and sibling group actions remain ambiguous.

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 covers 100% of the single parameter with a clear '群号' description. The tool description adds no parameter-level detail, but the baseline of 3 is appropriate because the schema already carries the semantic weight.

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 names a concrete action (打卡/check-in) and a resource (群内/in group), and specifies the delivery form as a sign-in card. It distinguishes the intent from message-sending siblings, though it could be more explicit about what 'sign' means.

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 send_group_msg, send_group_notice, or send_poke. There is also no mention of prerequisites such as whether the bot must be a group member or whether this replaces a manual check-in.

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