write_assembly

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

No annotations are provided, so the description carries the full burden. It does not say whether the write is patched into the binary, held in memory, whether it overwrites existing bytes, whether it requires an active session, or what happens to the instruction pointer. For a mutation tool with zero annotation coverage, this is a serious gap.

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?

Very short and front-loaded: purpose then a concrete example. It is efficient, though terse enough that the example ends up carrying more explanatory weight than it can support.

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?

An output schema exists, so return values need not be explained. But with no annotations, 0% schema coverage, and 3 parameters, the definition leaves the mutation semantics, parameter roles, and session/address prerequisites entirely undefined. It is insufficient for correct invocation.

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 only explains the 'assembly' parameter (mirroring the property title) and says nothing about 'address' (defaults to null, presumably the current address) or 'session_id' (defaults to null). The optional parameters remain ambiguous.

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 verb ('write') and resource ('assembly instruction (wa)'), and gives a concrete example, so the basic operation is clear. However, it does not distinguish itself from near-siblings such as write_hex, write_nop, set_register, or execute_command, and 'wa' is an unexplained abbreviation for an agent unfamiliar with the domain.

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 when-to-use guidance, no stated relationship to alternatives like write_hex/write_nop, and no preconditions (e.g., that a session must exist and an address must be current). The example illustrates syntax but not context of use.

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