set_motor_pwm_inversion

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

No annotations are provided, so the description must fully disclose behavior. It only states 'Invert PWM output polarity' and mentions a default, but fails to describe side effects, reversibility, or any impact on system operation (e.g., motor behavior). This is inadequate for a mutation tool.

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 extremely concise (two sentences), front-loads the action, and includes essential context (use case and default). No filler or 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?

For a simple parameter-setting tool with a single required parameter, the description provides purpose, use case, and default. It lacks explicit enumeration of valid values, but the overall context is sufficient for an experienced agent. Output schema is absent, but not critical here.

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 coverage is 100% (one parameter). The description adds the default value 'OFF', which is helpful, but does not enumerate acceptable values (e.g., ON/OFF, 0/1). The schema type is string, leaving ambiguity; the description's mention of 'UINT8' conflicts with the schema 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?

The description clearly states the tool inverts PWM output polarity, specifies the use case for ESCs requiring inverted signal, and names the resource 'motor_pwm_inversion'. This distinguishes it from numerous other set_* siblings.

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?

Provides explicit context for when to use: 'For ESCs that require inverted signal.' However, it does not mention when not to use it or alternative tools, though there are no direct competitors among siblings.

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