check_error

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

With no annotations, the description carries the behavioral burden and does so well: it discloses the read/clear side effect, the 16-entry limit, the first-only/No-error result, and the no-retries policy. It stops short of specifying exact return formatting or whether the clear always occurs.

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 entire description is one compact, front-loaded sentence with three high-value clauses: action/scope, return behavior, and retry policy. No filler or redundancy.

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 zero-parameter tool with no output schema, it specifies the input surface (none) and return behavior (first error or 'No error'), which is nearly complete. It could add the response shape or clarify whether clearing is unconditional, but the low complexity keeps the gap minor.

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 takes zero parameters, so the schema and context signals fully cover the parameter surface. The description adds no parameter detail, but none is needed; per the rubric, 0 params earns a baseline of 4.

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 identifies a precise action ('Read/clear') tied to a specific resource ('SCPI error entries') and states the output contract (return first or 'No error'), leaving no doubt about what check_error does relative to vague sibling names like idn or get_scope_state.

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 context is implied by the tool name and description: it is the error-checking operation among SCPI-related siblings. However, it never states when to choose this over scpi_execute or scpi_catalog, nor gives explicit exclusions.

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