ppsspp_list_scripts

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context by stating that the tool reads the in-memory manifest registry loaded at startup and does not execute any script. This goes beyond the structured annotations and clarifies the side-effect-free nature.

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 compact, front-loaded with purpose, and uses clear labeled sections (PURPOSE, USAGE, BEHAVIOR, RETURNS). Every sentence contributes useful information with no filler or 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 low-complexity read-only listing tool with one optional parameter and an output schema, the description is complete. It covers what the tool does, the filter options, behavioral guarantees, and the return envelope. Nothing needed for correct invocation is 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 description coverage is 100%, so the input schema fully documents the category parameter and its valid values. The description repeats this information and adds a return-shape hint, but it does not provide meaningful new semantics beyond what the schema already includes.

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 states a specific verb ('List') and a precise resource (diagnostic scripts declared in .ppsspp-dfx/config/scripts.manifest.yaml). It is clearly distinct from sibling tools like ppsspp_run_script and ppsspp_reload_scripts, and the 'Does not execute any script' note reinforces what this tool is for.

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 'USAGE' section explains the optional category filter and its valid values, but it does not explicitly say when to choose this tool over siblings or when not to use it. The intended use is implied rather than stated, and no alternatives are mentioned.

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