get_trigger_position

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

With no annotations provided, the description carries the burden, and it does disclose that the operation is a query (read-only) against the :TRIGger:POSition? register. It adds no detail on rate limits, permissions, or what the position value represents, but the read-only nature is the key trait here.

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?

A single sentence, front-loaded with the resource and the underlying SCPI command. No wasted words.

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 tool takes no arguments and an output schema exists, so the description need not explain the return value. It identifies the queried register and its read-only nature, which is sufficient for a simple scalar getter.

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?

Zero parameters, so there are no parameter semantics to explain beyond the implicit SCPI query target; baseline 4 applies.

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?

States a specific resource (trigger position in internal memory) and verb (query), which is clear enough to distinguish it from configuration siblings like get_trigger_config and get_trigger_status. It is terse but unambiguous about what is being read.

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 parenthetical 'query-only' hints that this is a read operation, but there is no guidance on when to use this vs. get_trigger_config, get_trigger_status, or the set_trigger_* siblings. No exclusions or prerequisites are stated.

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