desmume_read_register_packet

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that it reads a raw packet, with no mention of side effects, failure modes, or prerequisites. The return format and how the raw packet relates to emulator state are also undisclosed.

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 a single clear sentence with no wasted words. It is front-loaded with the action and resource, making it easy to parse quickly.

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?

The tool is simple, but the description is too terse to be fully complete. It does not explain what the raw ARM9 GDB register packet contains, when to use this read operation, or any dependencies on the emulator state. Without an output schema, the description should clarify the return value but does not.

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?

The tool has zero parameters, so the schema is empty and the description adds no parameter information. Per the baseline rule for 0-parameter tools, this is acceptable; no additional semantic clarification is needed.

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 clearly identifies the action ('Read') and the specific resource ('raw ARM9 GDB register packet'), distinguishing it from sibling tools like desmume_read_memory. The verb+resource pairing is unambiguous and specific.

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?

No guidance is provided on when to use this tool versus alternatives such as desmume_read_memory or desmume_capture_stop_context. The description only states what it does, without explaining the appropriate context or prerequisites (e.g., needing an active GDB connection or paused emulator).

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