anon_delete_qq_binding_group_open_id

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

The description adds real behavioral context beyond annotations (permission requirement, removal from qqGroups, auto-unbind on the QQ side, project inferred from the key). But it explicitly claims the operation is idempotent ('幂等') while the annotation declares idempotentHint=false, a direct contradiction on that flag. Contradicting a structured annotation caps this dimension despite the otherwise rich disclosure.

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?

Purpose is front-loaded in the first clause, followed by permission, side effects and the HTTP route. Dense and mostly waste-free, though the route line partially duplicates what the tool name already encodes.

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 destructive mutation with no output schema, the description covers the essentials an agent needs: required permission, what is mutated, idempotency behavior, project resolution, and an independent auto-unbind condition. Its only completeness failure is that the stated idempotency conflicts with the annotations.

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 the single nested groupOpenId parameter, so the description must compensate. It clarifies that the project component of the path is derived from the API key and need not be passed, which resolves a real ambiguity, but it adds no meaning about the groupOpenId value itself (format/origin).

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?

States a specific verb+resource: unbind ('解绑') a project's QQ group by groupOpenId, matching the DELETE route shown. The action is clearly distinct from the PATCH sibling anon_patch_qq_binding_group_open_id, though the description never names or contrasts a sibling explicitly, which keeps it from a 5.

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?

Provides useful preconditions (requires project:manage permission, project resolved from the API key so no projectId is passed) and describes an alternate trigger path (auto-unbind on GROUP_DEL_ROBOT). However it gives no explicit when-to-use vs when-not guidance and does not mention the PATCH binding sibling as an alternative.

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