ppsspp_read32

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

BEHAVIOR section states 'No side effects — pure read. PSP is little-endian. Returns an error if address+4 exceeds the valid memory region.' Annotations are absent, so description fully covers behavioral traits.

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?

Description is structured with clear sections (PURPOSE, USAGE, BEHAVIOR, RETURNS), front-loaded, and each sentence adds value. No filler.

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 simple 1-param read tool with no output schema, description covers purpose, usage, behavior, return format, and error condition. Complete for agent decision-making.

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 100% with detailed address explanation. Description adds no new parameter information beyond what's in the schema, so baseline of 3 applies.

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?

Description clearly states 'Read an unsigned 32-bit little-endian value from PSP memory at the given physical address'. It specifies verb, resource, and distinguishes from siblings by naming alternatives (read8/read16/read_range).

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?

Explicit USAGE section says 'Use for 32-bit fields — timestamps, large counters, pointers, RGBA colors. For 8/16-bit use ppsspp_read8/read16; for spans use ppsspp_read_range.' Provides when to use and alternatives.

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