发送标定参数

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

The description only states the action and parameters; it does not disclose potential side effects such as overwriting existing calibration or requiring a connection. With idempotentHint=false, the agent knows the operation is not idempotent, but the description adds no further behavioral context.

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 concise, consisting of two sentences. It front-loads the action and then clarifies parameters and purpose, with no redundant information.

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?

The description covers the tool's purpose, parameters, and the target system. While it does not mention prerequisites for communication or the exact return behavior, the presence of an output schema mitigates the need for return-value details. Overall, it is adequate for a simple send operation.

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?

The description explicitly defines each parameter: x and y as calibration point coordinates in mm, and r as the calibration angle. This provides crucial meaning beyond the input schema, which lists only bare numeric types with no descriptions.

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 a specific action: sending diffraction calibration parameters to the Hikvision vision host. It also explains the purpose (correcting coordinate mapping), which distinguishes it from sibling tools focused on movement, gripper control, and status checks.

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?

The description provides clear context by stating that the tool is used to correct the coordinate mapping relationship of visual detection. This implies when calibration is needed, though it does not explicitly exclude alternative tools or mention when not to use it.

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