sdg1062x_configure_burst

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

Annotations are all false but offer no positive safety hints. The description adds no behavioral context such as side effects on existing burst settings, required instrument connection state, or whether it enables burst mode. With annotations providing minimal value, the description carries the burden and fails to disclose meaningful behavior.

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 sentence with no wasted words, but it is so brief that it sacrifices essential detail. It is not verbose, but the extreme brevity limits its usefulness, making it merely average for this dimension.

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 tool with 7 parameters, no schema descriptions, and no useful annotations, the description is woefully incomplete. It fails to explain how to specify the channel, valid mode values, cycle counts, timing parameters, or trigger source, making it nearly impossible for an agent to invoke correctly without external knowledge.

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 0%, so the description must explain the parameters. It only hints at the 'mode' parameter by naming the three modes, but completely ignores cycles, channel, enabled, period_s, phase_degrees, and trigger_source. This is minimal and inadequate for a 7-parameter tool.

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 the specific verb 'Configure' with the resource 'burst behavior' and names the three modes (N-cycle, infinite, gated), which clearly identifies the tool's function. It distinguishes from sibling tools like configure_modulation and configure_sweep because it is specifically for burst, though it does not mention channel scope.

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 no guidance on when to use this tool versus alternatives, no prerequisites, and no conditions. It only states what it configures, leaving the agent without direction on selecting it over other configuration tools.

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