get_ieee488_status

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

With no annotations, the description carries the full burden and does disclose the critical behavioral trait: *ESR? is read-and-clears and *STB? clears the status byte, so calling it mutates state. That is exactly the kind of destructive side effect an agent needs. It does not cover polling frequency, timing, or failure modes, keeping it short of a 5.

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?

Two short paragraphs, front-loaded with the purpose and then the side-effect detail. The manual table references are slightly cryptic but do not bloat the text.

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?

An output schema exists, so return values need not be explained, and with zero parameters the description only needs purpose plus behavior — both are covered. Only the lack of routing guidance against sibling status tools keeps it from a 5.

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 the schema has nothing to explain and the baseline is 4. The description adds useful register-naming context but no parameter semantics are needed.

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 precise verb ('Read') plus the exact resources (*ESR?, *STB? and their enable masks *ESE?, *SRE?) and adds named-bit decoding. It is clearly distinguishable from the sibling set_ieee488_enable (which writes the masks) and from clear_status.

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 conveys context (this gathers status/event registers with decoding) but never states when to prefer it over get_status, get_errors, or clear_status, nor any preconditions. Usage is implied rather than prescribed.

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