Execute Processing

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

No annotations are present, so the description must fully disclose behavior. It mentions that memory layers are temporary, but fails to specify side effects, permission requirements, failure modes, or what the tool returns. This is insufficient for a complex tool that executes arbitrary algorithms.

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 concise with three sentences. The first sentence states the purpose, the second directs to a helper tool, and the third provides concrete parameter tips. Every sentence is informative and front-loaded.

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 complexity (executing any QGIS processing algorithm) and the absence of an output schema, the description is too brief. It does not explain error handling, return values, or the lifecycle of created layers. While referencing get_algorithm_help helps, the description itself is incomplete for safe and effective use.

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?

The input schema has 0% description coverage. The description adds value by explaining that layer parameters accept IDs or file paths and that OUTPUT can be set to 'memory:' for temp layers. However, it does not describe the algorithm parameter or the structure of the parameters object, leaving much to be discovered via get_algorithm_help.

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 'Execute a QGIS Processing algorithm' with a specific verb and resource. It references the related tool get_algorithm_help for parameter discovery, aiding understanding. However, it does not explicitly differentiate from siblings like run_model or batch_commands.

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 direct guidance: use get_algorithm_help to discover parameters, and specifies that layer params accept layer IDs or file paths and that OUTPUT should be set to 'memory:' for temporary layers. It lacks explicit when-not-to-use or alternatives, but the provided advice is actionable.

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