ppsspp_breakpoint_list

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

Declares 'BEHAVIOR: No side effects — pure read.' Without annotations, the description fully covers behavioral traits, assuring the agent of safe, read-only operation.

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?

Well-structured with clear section headers (PURPOSE, USAGE, BEHAVIOR, RETURNS). Each of the four sentences serves a distinct purpose 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 list tool with no parameters and no output schema, the description covers purpose, usage, behavior, and return format. Could mention sibling distinction, but overall sufficient.

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?

Input schema has zero parameters (100% coverage). Description adds no parameter details, but no parameters exist. Baseline of 4 for zero-parameter case is appropriate.

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 explicitly states 'List all currently-set CPU execution breakpoints', using specific verb and resource. Clearly distinguishes from sibling tools like ppsspp_breakpoint_add and ppsspp_breakpoint_remove.

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?

Provides explicit when-to-use instructions: 'Inventory before bulk-removing, or sanity-check what's set.' While no explicit alternatives or when-not-to, the context makes it clear it's for listing only.

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