execute_code

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

No annotations are provided, so the description carries full burden. It states the tool executes code but doesn't disclose critical behavioral traits: whether it's safe/destructive, what permissions or environment it runs in, if there are time/rate limits, what happens on errors, or the output format. For a code execution tool with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place without redundancy or fluff.

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 complexity of executing arbitrary code, lack of annotations, no output schema, and low parameter coverage, the description is incomplete. It doesn't address safety, error handling, return values, or execution context, which are crucial for an agent to use this tool effectively. The minimal description is inadequate for the tool's potential impact.

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 mentions 'code provided as a string' which aligns with the 'code' parameter, adding minimal semantics. However, it doesn't explain what constitutes valid PyQGIS code, expected syntax, imports, or constraints, leaving the parameter poorly defined beyond its type.

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 ('arbitrary PyQGIS code provided as a string'), making the purpose understandable. It distinguishes from siblings like 'execute_processing' by specifying 'PyQGIS code' rather than processing algorithms. However, it doesn't explicitly differentiate from other code execution tools that might exist, keeping it at 4 rather than 5.

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 no guidance on when to use this tool versus alternatives. With siblings like 'execute_processing' for specific algorithms and other tools for layer/project operations, there's no indication of appropriate contexts, prerequisites, or exclusions. This leaves the agent without usage direction.

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