scpi_execute

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

With no annotations provided, the description carries the full burden and succeeds admirably. It discloses destructive capabilities (overwrite files, reset, change LAN or lock controls), non-reset write error draining, query status/error consumption, and lack of retries or completion guarantees. This is exemplary transparency.

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 dense and information-rich with zero filler. The core purpose is front-loaded in the first sentence, and each subsequent sentence adds a distinct behavioral or usage constraint. Every word earns its place.

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?

This is a complex, dangerous tool with 6 parameters and no output schema, and the description covers safety, side effects, data handling, and execution semantics exceptionally well. The only notable gap is the absence of return-value/response format information, which matters because no output schema exists to fill that void.

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?

Schema description coverage is only 50%, but the description compensates by adding critical meaning: positional argument ordering, inline_binary size limit of 1024 bytes, and file-backed handling for large text/binary data. This significantly clarifies parameters not described in the schema.

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 the specific action (execute) and resource (one DHO814 catalog command), and mentions positional arguments, which distinguishes it from catalog listing tools like scpi_catalog. The purpose is immediately understandable and unique among siblings.

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 extensive usage context, including data size limits, file-backed handling, scope-enforced limits, error-draining behavior, and safety caveats. It does not explicitly name alternative tools or give when-not-to-use conditions, but the contextual guidance is strong enough to guide correct invocation.

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