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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds crucial behavioral context: it runs a model, takes up to 2.5 minutes, and advises against consecutive calls. It also explains the dynamic default for scope and that groupCount may be silently clamped. No contradiction with 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 tightly structured with labeled sections (【需要登录·主办方】【何时用】【组合链】【口径】). It front-loads the purpose and usage, then provides bullet-pointed notes. Every sentence adds value; no filler. It is compact yet comprehensive.

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?

Covers prerequisites (login, organizer), the exact workflow (start → poll → publish), timing cautions, parameter defaults and clamping, and a rejection condition. There is no output schema, but the description indicates the next step in the chain, so an agent knows what to expect and how to proceed. Nothing critical 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 already documents all parameters (100% coverage), so baseline is 3. The description goes beyond the schema: it clarifies the default behavior of scope when omitted, explains server-side clamping of groupCount, and notes the rejection condition when too few people. This adds meaning beyond the raw schema definitions.

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: initiates a regrouping round for on-site icebreaking. The description names the exact context ('现场要分组破冰时') and differentiates from siblings via the explicit chain (start → poll → publish). It is clear what the tool does and where it fits.

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?

Gives explicit when-to-use ('现场要分组破冰时'), a usage chain, and exclusions: '不要连着发起第二轮', '人太少会被拒', and scope default behavior. It tells the agent exactly when to call this vs. the publish step, and what conditions gate it.

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