Execute Processing

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

With no annotations, the description carries the full burden. It discloses key behavioral traits: timeout cancellation (default 55 seconds), the blocking nature of long jobs holding the QGIS session, and the memory output option. It doesn't specify return values or side effects, but for an algorithm-agnostic executor, the stated behaviors are important and useful.

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 four sentences, front-loads the main purpose, and every sentence adds value. It covers parameter usage, timeout, and operational caveats without fluff or repetition.

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?

Given the tool's dynamic nature (arbitrary QGIS algorithms) and the absence of both annotations and an output schema, the description covers the most critical operational context: parameter discovery, layer input formats, temp output, and timeout/blocking behavior. It could also mention error handling or return values, but the open-ended nature makes this a reasonable trade-off.

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 coverage is 0%, so the description compensates by explaining the 'parameters' object (layer params accept IDs/paths, OUTPUT='memory:') and the 'timeout' parameter (default 55, cancellation behavior). The 'algorithm' parameter is self-explanatory by name. This adds real meaning beyond the bare 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?

The description opens with 'Execute a QGIS Processing algorithm', giving a specific verb and resource. It distinguishes itself from siblings like execute_processing_batch and run_model by focusing on a single algorithm execution, and it points to get_algorithm_help for parameter discovery.

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 provides clear context on how to use the tool: use get_algorithm_help to discover parameters, layer params accept IDs or paths, set OUTPUT to 'memory:' for temp layers, and adjust timeout for heavy work. While it doesn't explicitly state alternatives/exclusions (e.g., batch processing), the context is solid and practical.

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