push_set_pad_color

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

With no annotations, the description carries the transparency burden. It discloses hardware requirement, return value ('sent=true'), and that the pad and color are 'accepted by the bridge'. It could mention error scenarios or side effects, but overall is fairly transparent.

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 sentences with no wasted words. The first sentence states the core action; the second adds context (use case, requirement, return). Front-loaded and efficient.

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 two-parameter tool with no output schema, the description covers purpose, use case, requirement, and return value. Missing details about color semantics or behavior on duplicate pads, but adequate given the tool's simplicity.

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?

The description does not add meaning for the 'color' parameter (e.g., what values 0-127 correspond to), and the schema only describes 'pad'. With 50% schema coverage, the description should compensate but fails to describe 'color' beyond its existence.

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?

Clearly states the verb 'Set' and resource 'color of one Ableton Push 2/3 pad on the 0..63 grid'. The phrase 'Use for visual feedback or performance layouts after hardware detection' further clarifies purpose and distinguishes from siblings like push_set_button_led.

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 usage context ('visual feedback or performance layouts after hardware detection') and requirement ('Requires Push 2/3'), but does not explicitly state when not to use this tool or mention alternative tools like push_set_button_led for button LEDs.

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