DebugSetVariable

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

No annotations exist, so the description carries the full burden. It does disclose the stopped-debuggee and non-batch preconditions, but it labels the operation '[read-only]' even though it mutates debuggee state by setting a variable — an actively misleading signal. Nothing is said about side effects, what happens if the debuggee resumes, or the failure mode when the handle is stale.

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 bracketed/sentence fragments, front-loaded with the operation and its preconditions. No wasted text, though the '[read-only]' token is worse than wasted — it is a cost.

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 4-parameter mutating debug tool with no annotations and no output schema, the definition covers only preconditions. It does not describe the return shape of the set operation, what the 'detail' enum changes about the response, or error behavior when the debuggee is running — gaps the agent must discover at call time.

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%, so name, value, detail, and state_handle are already documented with path, type-conversion, and verbosity behavior. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

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 a variable of the stopped debuggee' — which clearly separates it from DebugGetVariables and the DebugStep family. It lacks the state_handle/scope specifics that would make it a 5, but the core action is unambiguous.

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 two concrete preconditions that gate invocation: a stopped debuggee is required, and it runs outside batch mode. It does not point to alternatives (e.g., DebugGetVariables to read first, or DebugBatchBegin for batch usage), so it stops short of a 5.

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