set_adapter_speed

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

Goes meaningfully beyond the annotations by disclosing the default ST-Link speed (~480 kHz), the expected ~8x throughput gain, and the failure condition that should trigger a reduction. It does not explain persistence (session-scoped vs. global) or why the tool carries destructiveHint=true, leaving the flagged destructiveness unexplained.

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 tight sentences with the action front-loaded and the performance/risk trade-off following. No filler; every sentence carries information an agent can act on.

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 two-parameter config tool with annotations covering the mutation profile and no output schema, the description supplies enough context to call it correctly. The only material omission is whether the setting persists across sessions or only affects the current target.

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 100% — both khz and session are documented in the schema, including the 'e.g. 4000' example. The description reinforces the practical meaning of khz but adds no syntax or format detail beyond the schema, and never mentions the session parameter, so the baseline 3 applies.

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 — 'Sets the SWD/JTAG adapter clock (kHz) at runtime' — with units and mechanism. No sibling tool changes adapter clock speed, so it is trivially distinguishable from the rest of the list.

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?

Gives concrete when-to guidance in both directions: raise it (e.g. 4000) to speed flashing and memory reads, lower it if reads/flash become unreliable. It stops short of naming prerequisites or the alternative of leaving the default, but the tuning context is clear.

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