ppk2_configure

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

Without annotations, the description properly discloses key behaviors: opens serial port if not already open, reads calibration, selects mode, sets voltage. It also describes mode-specific behavior (voltage_mv usage in ampere vs source). However, it doesn't mention error conditions or what happens on failure, though output schema may cover return values.

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 concise and well-structured: a one-sentence summary, followed by detailed behavioral steps, then clear argument explanations. Every sentence adds value with no redundancy.

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?

The description covers the main function, all parameters, usage sequence, and mode-specific behavior. Output schema exists for return format. Minor omission: no mention of behavior on repeated calls or error handling, but overall it's sufficiently complete for a configuration 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?

Schema has 0% description coverage, but the description adds extensive meaning: mode options with detailed explanations (external vs source), voltage_mv range (800-5000) and purpose, port override mechanism. This fully compensates for the schema's lack of descriptions.

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 'Open the PPK2 and configure it for measurement' with specific verb and resource. It distinguishes from siblings by mentioning 'Call this before `ppk2_measure`' and referencing `ppk2_power` for enabling output, making its unique role evident.

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 says 'Call this before `ppk2_measure`' and explains when to use each mode ('ampere' vs 'source'), including that 'ampere' mode requires external supply and 'source' mode needs `ppk2_power("ON")`. This provides clear context for usage and alternatives.

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