ps_get_range

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

Annotations already declare readOnlyHint=true, so the agent knows it's a safe read operation. The description adds no additional behavioral traits (e.g., whether it fetches the current range setting, if it affects device state, or response structure). It fails to add value beyond the annotation.

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 (a single phrase), which can be concise but here it is under-specified. It does not front-load the most critical information (e.g., what it returns). Every word is present, but the content is insufficient for effective tool selection.

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 the tool's simplicity and presence of an output schema, the description still falls short. It does not explain the return value (e.g., what the range represents, units) or the device state required. Without additional context, the agent may misinterpret the tool's behavior.

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% and the description does not explain any parameters. Both 'alias' and 'params_json' remain opaque. The description adds no meaning to the input schema, leaving the agent to guess parameter purpose and format.

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 indicates a query for voltage range, specifying both the action (query) and resource (voltage range). It distinguishes from sibling tools like ps_get_voltage (get voltage) and ps_get_current (get current). However, it is minimal and lacks explicit context, such as what 'range' refers to (e.g., set range limit or actual range).

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 is provided on when to use this tool versus alternatives (e.g., ps_get_voltage, ps_meas_voltage). It does not specify prerequisites, typical scenarios, or when not to use it. The description offers no exclusions or context for selection.

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