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

The description states that formSchema is a whole-table overwrite where omitted questions are deleted ('遗漏题会删除'), which is a destructive update. The annotations declare destructiveHint=false, so the description directly contradicts the annotation. Despite other rich behavioral context, the contradiction mandates a score of 1.

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 dense but front-loaded: the core action and immediate effect come first, followed by the composition chain and edge cases. Each sentence appears to carry necessary behavioral guidance, though the bracketed style is tightly packed rather than flowing; minor streamlining is possible without losing meaning.

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?

Given 8 parameters, a nested formSchema array, no output schema, and the update's complexity, the description covers login requirement, immediate effect, composition chain, deadline alternative, overwrite semantics, baseline supplementation, disallowed keys, and signupUrl delivery behavior. It is complete enough for an agent to call correctly aside from the already-flagged annotation contradiction.

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 coverage is 100%, so baseline is 3. The description adds meaning beyond the schema: it explains formSchema overwrite semantics (missing questions deleted, no further auto-learning, must bring back sensitive/sourceLabel), hostedEnabled baseline supplementation of 7 system questions, signupUrl delivery recalculation, and that adapterKey/deliveryMode are not organizer-editable. Some params (e.g., articleUrls, contactNote) receive no extra description, hence not a 5.

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 specific verb (改) and resource (报名配置), enumerates affected fields (题目/类目/外表/群码), notes immediate effect, and explicitly distinguishes from update_activity for deadline changes. An agent can tell what this tool modifies without opening the schema.

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 an explicit composition chain (get_organizer_activity → pass only changed items → re-read to confirm) and names update_activity as the alternative for deadline changes. It also warns that advancing a deadline blocks active form-fillers and requires prior confirmation, so both when-to-use and when-not-to-use are covered.

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