ppsspp_analyze_log

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

Annotations already mark it read-only and non-destructive, but the description adds valuable behavioral context: it explicitly says 'READ-ONLY', 'Does not contact PPSSPP', and clarifies that it only reads and filters a log file. This goes beyond the annotations and removes any ambiguity about side effects.

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 well-structured with PURPOSE, USAGE, BEHAVIOR, and RETURNS sections. Every section is short, informative, and front-loaded with the tool's core purpose. No filler or redundant explanation.

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 read-only log filter tool, the description covers the purpose, default path, optional filter behavior, side-effect-free behavior, and return shape. The rich parameter schema and output schema cover the remaining details, making the definition complete for an agent to call it correctly.

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 schema already documents each parameter well, including defaults, whitelist restrictions, and case sensitivity. The description summarizes defaults but does not add substantial new parameter semantics beyond what the schema provides.

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 states a specific verb ('Filter'), a specific resource ('PPSSPP log file'), and explicit line types (ERROR/WARNING/CRASH). It clearly distinguishes this from the many sibling PPSSPP tools, none of which are log-filtering tools.

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 gives clear usage context: log_path is optional with a documented default, filter is an optional keyword, and session_id is reserved. It does not explicitly state when not to use it or compare against alternatives, but the tool's function is unique among siblings and the usage section is concrete.

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