write_register

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does disclose that `value` is a gdb expression, which is useful, but it omits side effects, whether the target must be stopped, how register name should be formatted, and what happens after the write.

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?

The description is two sentences with no waste, front-loading the operation and immediately providing the key parameter clarification. Every sentence contributes useful information.

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 mutation tool with no annotations, no output schema, and 0% schema coverage, the description is too sparse. An agent still lacks clear details about the `name` parameter, session context, expected results, and error conditions, making correct invocation dependent on assumptions.

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 must compensate. It usefully explains the `value` parameter with concrete gdb expression examples, but it does not clarify `name` (presumably the register name) or `session_id`, leaving those meanings to be inferred.

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 clear verb ('Write') and resource ('register'), so an agent can tell this sets a register value. It does not explicitly distinguish itself from siblings like write_memory or execute_command, though 'register' in the resource makes the target reasonably clear.

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?

There is no guidance on when to use this tool instead of alternatives, such as write_memory for memory changes or execute_command for arbitrary gdb commands. The description implies you use it when you need to set a register, but it doesn't state prerequisites like an active session or stopped process.

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