usbtmc_send

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

The description discloses that this function only sends data and does not read responses, and it outlines the return dict structure. It also notes the need for separate receive/query operations. This adds context beyond the annotations, though it does not discuss potential device-side effects or idempotency nuances. Minor inconsistency with schema examples querying commands, but overall transparent.

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 well-structured with purpose, usage guidance, args, and returns. It is reasonably concise, though the usage guidance and send-only note are slightly repetitive. Every sentence earns its place, but the redundancy prevents a perfect score.

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?

Given the tool's simplicity and the presence of an output schema, the description covers the essential aspects: what it does, when to use it, parameters, and return values. It does not mention error handling or edge cases, but the return message field addresses that. Overall, it is complete for practical use.

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 schema already provides detailed descriptions for device_id and command, including examples. The description's Args section repeats this information without adding new semantic meaning. It does helpfully frame the command as a SCPI string and device_id as a connection identifier, but this does not significantly exceed schema coverage.

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 'Send a SCPI command to a specific USBTMC device' with a specific verb and resource. It also distinguishes itself from siblings by explicitly directing query commands to usbtmc_query(), making its purpose unambiguous.

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 explicitly tells the agent when to use this tool ('Use for SET commands (without '?')') and when to use alternatives (usbtmc_query() for queries, usbtmc_receive() for reading responses). This is model guidance with named alternatives.

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