dpo2012b_query_binary

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read nature is known. The description adds the key behavior that the response is Base64-encoded binary data and that the query must be documented, but it does not disclose error behavior or prerequisites like an active connection.

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 one concise, front-loaded sentence with no filler. Every phrase contributes meaning: it states the action, the object, and the output format.

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?

Although the tool has an output schema and only one parameter, the description alone is insufficient for reliable invocation. It lacks command examples, accepted query syntax, and usage context, making it incomplete for an agent.

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?

With 0% schema description coverage, the description must compensate for the 'command' parameter. It hints that 'command' is a binary query, but it does not specify the command format, allowed values, or syntax, leaving a significant gap for the agent.

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 uses a specific verb ('Run') and identifies a distinct resource ('documented binary query'), plus specifies the return format (Base64). This distinguishes it from sibling tools like dpo2012b_query_scpi, though 'documented' is somewhat vague.

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 phrase 'binary query' implies this tool is for binary requests rather than textual SCPI queries, and the sibling dpo2012b_query_scpi is an evident alternative. However, there is no explicit guidance on when to choose this over the text query tool or what counts as a 'documented' query.

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