esr

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

The 'readOnlyHint' annotation is true, and the description says '读取' (read), which aligns. However, the description adds no additional behavioral context beyond the annotation, such as side effects or error handling. No contradiction detected.

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 very short (one phrase), which is concise but lacks structure. It is not front-loaded with critical information, and the brevity comes at the cost of completeness.

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, the description fails to explain the tool's behavior, how to use parameters, or what the tool returns. The presence of two unannotated parameters and no contextual hints leaves gaps 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 explain the two parameters (alias and params_json). The tool relies on these parameters, but the agent receives no guidance on their purpose or format, making effective use impossible.

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 states '读取事件状态寄存器' which is Chinese for 'read event status register', a specific verb+resource. However, it lacks differentiation from sibling tools like scpi_query or idn, and the '[GENERIC]' prefix suggests it's a generic SCPI command without clarifying its uniqueness.

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 vs alternatives. There is no mention of context, prerequisites, or exclusions, making it difficult for the agent to decide when to invoke this tool over other query tools.

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