ps_get_ovp

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

Annotations already declare readOnlyHint=true, and the description confirms it is a read operation ('查询'). However, no additional behavioral traits are disclosed, such as return format, potential errors, or that it fetches from instrument memory. The output schema exists but is not described.

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 and to the point, wasting no words. However, it lacks structure and could benefit from additional detail without sacrificing conciseness.

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?

For a simple query tool with existing annotations and an output schema, the description is incomplete. It does not mention what the output contains (e.g., the protection value or status) or any prerequisites, making it less helpful for the agent.

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 mention any parameters. Neither 'alias' nor 'params_json' are explained in the description, leaving the agent without guidance on how to use them beyond default values.

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?

Description clearly states it queries an overvoltage protection value, using a specific verb and resource. It distinguishes from siblings like ps_get_ocp and ps_get_voltage by specifying 'ovp', but could be more explicit by adding 'Keysight power supply' context.

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_ovp or other ps_get_* tools. The description only states the action without any context about scenarios or comparisons.

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