ps_set_range

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

Annotations indicate destructiveHint=false, but the description does not add behavioral context such as side effects, authorization needs, or what happens to other settings. It simply restates the action without elaboration.

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 extremely short (one phrase), which is concise but sacrifices necessary information. It is front-loaded with the action, but every sentence (word) does not earn its place given the lack of parameter details.

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?

Despite having an output schema (not provided in the description), the tool lacks parameter explanations, return value hints, and any context about when setting voltage range is appropriate. The description is incomplete for meaningful use.

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 has 0% description coverage for parameters 'alias' and 'params_json', and the tool description does not explain their meaning or usage. The agent has no clue what values to provide, making it effectively unusable.

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 action (set voltage range) and the resource. It matches the tool name and distinguishes from siblings like ps_set_voltage or ps_set_current, though no explicit differentiation is provided.

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 on when to use this tool versus alternatives like ps_set_voltage or ps_get_range. The description implies usage for setting voltage range, but lacks context for exclusions or prerequisites.

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