get_cursor_values

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

With no annotations, the description carries the behavioral disclosure burden. It adds meaningful semantic context by explaining that AX_s/BX_s are in seconds, XY axes are amplitudes, and inv_delta_x is reciprocal separation rather than signal frequency. This helps prevent misinterpretation of returned values.

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 compact and front-loaded with the core purpose, followed by two short sentences that clarify unit semantics. Every sentence adds useful information with no filler.

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 parameterless read tool, the description covers the essential behavior and key value semantics. It does not specify the exact return shape or mention whether cursors must be previously configured, but the low complexity and clear field explanations make it reasonably complete.

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 tool has zero parameters, so parameter documentation is not needed. The description instead clarifies the meaning of the returned values, which is the relevant semantic content for this parameterless read tool.

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 identifies a read operation on cursor values plus DHO source/type, using a specific verb and resource. It is distinguishable from siblings like set_cursors, though it does not explicitly name alternatives or contrast itself with other read tools.

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?

Usage is implied: use this tool when you need to read cursor values rather than set them. However, the description does not explicitly state when to prefer this over related measurement tools, nor does it mention any prerequisites such as active cursors.

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