desmume_read_memory

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

With no annotations, the description carries the full burden for behavioral disclosure. It mentions the GDB RSP mechanism and the 4096-byte cap, but omits error behavior, return format, and the impact of invalid addresses. The phrase 'at most' hints at partial reads but does not explain why.

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, front-loaded sentence with no wasted words. It succinctly communicates the core operation and constraint.

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?

Given no output schema or annotations, the description should explain return values, failure modes, and the dependency on an active GDB session. It does none of these. The brief description is sufficient only if the agent already understands the debugger context from sibling tools.

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%, and the description adds little beyond the schema. 'Address' and 'length' are self-explanatory from the property names, and the 4096-byte maximum repeats the schema constraint. No additional meaning is provided for special cases like endianness or memory regions.

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 states the verb ('read'), resource ('ARM9 memory'), and constraint ('at most 4096 bytes'), and it distinguishes from sibling tools like desmume_read_register_packet by specifying memory rather than registers.

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 given on when to use this tool versus alternatives such as nds_inspect_rom, nor are prerequisites like an active GDB connection mentioned. The description only states what it does, not when to choose it.

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