burst

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

Discloses key behaviors: temporary effect, automatic fallback, need for channel to be running, and suggestion to pause after use. No annotations, but description covers main traits. Minor gap: no mention of safety or return values.

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?

Description is concise and front-loaded with action, then trigger/avoid, then constraints. Efficient but could slightly tighten phrasing.

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 purpose, usage guidelines, and constraints. Lacks explicit mention of return value or status, but given simplicity and lack of output schema, it is sufficiently complete.

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 provides full descriptions for all 3 parameters. Description adds usage context (duration range, strength subject to limits) but doesn't significantly enhance parameter meaning beyond schema.

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 clearly states the tool's action: temporarily pull a running channel to a target strength and then automatically fall back. It distinguishes from siblings by specifying when not to use (channel not started, long-term strength).

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?

Includes explicit trigger condition ('制造短促峰值、强烈点射感时使用'), avoid conditions ('通道未启动', '想长期提升强度'), and a constraint (max 1 call per round).

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