ppk2_power

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

Describes internal actions (enable/disable voltage, connect/disconnect switch) and prerequisite. No annotations provided, so description carries full burden; lacks details on side effects or state persistence.

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?

Front-loaded with main purpose, mode explanation, and prerequisite. Could be slightly more concise, but structure is clear.

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 prerequisite, mode behavior, and parameter values. Output schema exists (not shown), so return value not needed. Adequate for a simple on/off tool.

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?

Only parameter 'state' has no schema description; description provides valid values 'ON' or 'OFF' in Args, adding meaning beyond the schema's generic string type.

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?

Clear verb and resource: 'Turn the DUT power output ON or OFF.' Explains behavior in source and ampere modes, and distinguishes from sibling tools by focusing on power control.

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?

States prerequisite: requires `ppk2_configure` first. Explains mode-dependent behavior. Lacks explicit comparison to alternatives but provides sufficient context.

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