bizhawk_read_memory

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

No annotations are provided, so the description carries full behavioral burden. It doesn't disclose whether this is a safe read operation, what happens on invalid addresses, whether the returned data is in a specific byte order or format, or how the GB wrapper maps to System Bus addresses. The word 'wrapper' suggests it delegates to emulator_read_memory but the behavioral differences (if any) are unstated.

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 short sentence with no waste, which is technically concise. However, it's under-specified rather than efficiently complete — a concise but nearly empty description. For a one-line wrapper description it achieves minimal length but sacrifices meaningful content.

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?

This is a moderately complex tool (3 parameters, GB address translation wrapper, no annotations, no output schema) yet the description is a single phrase. It doesn't explain GB memory banking, address valid ranges, the relationship between domain and GB addresses, or return value semantics. The wrapper concept introduces translation complexity that is entirely unexplained.

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, but it adds nothing about parameters. The address parameter accepts integer or string (likely hex) — the description doesn't clarify string format (e.g., '0x2000' vs decimal), and domain/length defaults are undocumented. The 'GB-compatible' hint implies address semantics differ from raw System Bus but doesn't explain how.

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 'GB-compatible wrapper for emulator_read_memory' identifies the tool as a wrapper for the sibling emulator_read_memory, giving it some directional clarity for GB (Game Boy) addresses. However, it doesn't explicitly state what the tool DOES (reads memory) with a clear verb+resource, instead relying on the reader to know that emulator_read_memory reads. It does weakly distinguish from siblings but the purpose remains implied rather than stated.

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?

The description hints this is for GB-compatible addresses, implying it should be used instead of emulator_read_memory when working within the GB memory mapping. But it provides no explicit when-to-use vs when-not-to-use guidance, no mention of address range constraints, no formatting details, and doesn't state why a GB wrapper exists (e.g., address translation, banking).

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