ppsspp_read8

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

No annotations provided, so description fully carries burden. Clearly states no side effects (pure read), and that it returns an error if address is invalid. Also describes the return format.

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 concise with labeled sections (PURPOSE, USAGE, BEHAVIOR, RETURNS) that front-load key information. Every sentence adds value without redundancy.

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 read tool with one parameter and no output schema, description covers purpose, usage context, behavioral traits, return format, and error handling. Nothing missing.

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 provides detailed description of the address parameter (100% coverage). Description adds further context on PSP memory layout (user RAM, kernel RAM, VRAM, etc.), enhancing understanding beyond schema.

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?

Clearly states it reads an unsigned 8-bit byte from PSP memory at a physical address. Distinguishes from siblings by mentioning alternative tools for other data widths (ppsspp_read16/read32) and ranges (ppsspp_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?

Explicitly states when to use: for single-byte fields, counters, etc. Provides alternatives for other scenarios, e.g., for 16/32-bit values or spans.

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