set_bluetooth_name

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so the safety profile is covered. The description adds real value beyond them: the change only takes effect after the pedal is switched off and on, and the candid "Unverified" note warns the agent that the operation's behavior has not been confirmed. It stops short of describing failure modes or what happens if the name is rejected.

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?

Three short sentences, front-loaded with the action, then constraint, then effect timing, then a caveat. Every sentence earns its place and nothing is repeated from the schema or annotations.

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 one-parameter mutation with no output schema, the description covers constraint, activation latency, and a verification caveat — enough to call it correctly and set expectations. It could go slightly further by saying whether a retry is safe or how to confirm the new name took effect.

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 0%, so the description must carry the meaning of the single `name` parameter, and it does: 1-17 printable ASCII characters in total, with a fixed "M2" prefix included in that count. This is genuinely new information the schema's minLength/maxLength do not convey. It omits what happens on invalid input, keeping it below a 5.

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?

States a specific verb and resource: "Rename the pedal's Bluetooth name." It is unambiguous and does not overlap with any sibling tool (none of the other tools touch Bluetooth), so an agent can select it without further inference.

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?

Usage is implied by the purpose rather than stated: there is no explicit when-to-use, when-not-to-use, or alternative named. What it does offer in place of routing guidance is operational context (character constraints, activation requires a power cycle), which helps an agent decide whether the timing is acceptable.

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