set_sd_mux

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

Annotations already indicate the destructive nature, so the description doesn't need to repeat that. It adds the constraint that the place must be 'acquired', which is useful behavioral context beyond the annotations. However, it doesn't elaborate on potential side effects or failure modes.

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 a single, concise sentence that is front-loaded with the action and resource. No filler words; every word contributes to the meaning.

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 existence of an output schema and annotations covering safety, the description is adequate for a simple tool. It mentions the key precondition ('acquired place') but leaves out parameter details and alternative tool guidance, making it incomplete for a fully unassisted agent.

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?

With 0% schema description coverage, the description provides some meaning: 'mode' is the SD mux mode and 'place' is the acquired target. It does not enumerate valid mode values or clarify the place format, but it does offer basic semantics for both parameters.

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 the tool's function: setting the SD mux mode on a place. It uses a specific verb+resource construction and the mention of the driver call (USBSDMuxDriver.set_mode()) further disambiguates it from related tools like set_usb_mux.

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 implies usage on an 'acquired place', which is a prerequisite, but does not explicitly state when to use this tool over siblings or provide exclusions. The context is clear but alternatives are not discussed.

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