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 that the tool executes an algorithm (a write operation) and gives some parameter hints, but it does not describe side effects, whether it is destructive, or what happens to existing layers.

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 three concise sentences, each adding value. The main action is first, followed by a tip and parameter hints. No 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?

Given no output schema and nested objects in parameters, the description should provide more comprehensive guidance on parameter structure and return values. While it mentions 'memory:' for output, it does not describe the return value or behavior beyond execution.

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 0%, so the description must compensate. It adds meaning by explaining that layer params accept IDs or file paths and that OUTPUT can be set to 'memory:'. However, the general structure of the parameters object is not explained, leaving gaps.

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 clearly states the action 'Execute' and the resource 'a QGIS Processing algorithm'. However, it does not differentiate from sibling tools like 'execute_processing_batch' or 'raster_calculator', which could also execute algorithms.

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 guidance on using 'get_algorithm_help' to discover parameters and mentions that layer params accept IDs or file paths. However, it does not specify when to use this tool vs. alternatives like the batch version or when not to use it.

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