scope_connect

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

Discloses transport (local VISA session) and action (queries *IDN?), returning IDN string. Does not mention potential side effects like session locking or need to disconnect.

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?

Efficiently structured with purpose first, then details; no wasted words, though could be slightly more compact.

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?

Covers purpose, parameter, output, and transport. Lacks error handling or dependency notes, but sufficient for its simple role given the output schema exists.

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?

Adds substantial meaning beyond the schema (which has 0% coverage) by providing a clear example and format description for resource_string.

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 'Connect to the LeCroy oscilloscope' with specific verb and resource, and distinguishes from siblings like scope_disconnect and scope_list_resources.

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?

Implied usage (connect before other operations) but no explicit when-to-use, prerequisites, or alternatives like scope_list_resources for finding addresses.

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