pad_trigger

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

No annotations are provided, so the description carries the full behavioral burden. It usefully explains that the trigger persists without hold_ms and releases after hold_ms, but it omits side handling, interaction or override semantics with other pad controls, and any error/return 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?

Two short sentences are front-loaded with the core action and range, followed immediately by the hold_ms conditional. There is no redundant or filler text.

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 three-parameter input tool with no annotations or output schema, the description covers the key hold/release semantics and percent range. It is still incomplete because the required side parameter and sibling selection guidance are absent, leaving inference to the schema and surrounding context.

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 should explain all three parameters. It adds meaning for percent range and hold_ms persistence/release behavior, but it never explains the required side parameter or its left/right enum.

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 states a specific verb and resource: "Set an analog trigger" with a percent range. It is clear, but it does not differentiate from nearby siblings like pad_press, pad_down, pad_up, or pad_stick, nor does it mention the required side dimension.

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?

No when-to-use, when-not-to-use, prerequisites, or alternative tools are named. The only conditional is the hold_ms behavior, which describes mechanics rather than selection guidance.

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