Execute Processing

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

No annotations are provided, so the description carries the full burden. It does not disclose any side effects, destructive behavior, authorization needs, or return values. The hints about parameter types are helpful but insufficient for behavioral transparency.

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?

Three short sentences with no redundant information. Every sentence adds value: purpose, referral to help tool, and parameter tips.

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?

The description is adequate for a tool with no output schema and two parameters, but it lacks information on return values (e.g., results, errors) and whether execution is synchronous. Given the complexity of processing algorithms, more context would be beneficial.

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 must compensate. It adds meaning by explaining that algorithm is a string referencing a processing algorithm and that parameters is a JSON object. It also provides guidance on layer params and OUTPUT, partially compensating for missing schema descriptions.

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', which is a specific verb+resource. It also references get_algorithm_help for parameter discovery, distinguishing it from sibling tools like add_vector_layer or execute_code.

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?

It advises using get_algorithm_help to discover parameters, and provides practical tips on layer IDs/file paths and 'memory:' for temp layers. However, it doesn't explicitly state when not to use this tool or mention alternatives.

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