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 of behavioral disclosure. It fails to describe any behavioral traits: it doesn't specify if this is a read-only or destructive operation, what permissions or authentication are required, whether it has side effects (e.g., modifying data or projects), rate limits, error handling, or output format. For a tool with 'execute' in its name and no annotations, this lack of transparency is critical and could lead to unsafe or incorrect usage.

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 that directly states the tool's action without unnecessary words. It's front-loaded with the core purpose ('Execute a processing algorithm'), making it easy to scan. Every part of the sentence earns its place by conveying essential information, though it lacks depth due to its brevity.

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 implied by 'execute' and processing algorithms, along with no annotations, 0% schema description coverage, no output schema, and nested parameters, the description is incomplete. It doesn't address what the tool returns, how algorithms are defined, error conditions, or integration with sibling tools (e.g., whether it works on layers from 'get_layers'). For a potentially powerful execution tool, this leaves too many unknowns for reliable 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 description mentions 'parameters' but adds no meaning beyond what the input schema provides. With 0% schema description coverage, the schema only lists 'algorithm' (string) and 'parameters' (object) without explaining what algorithms are available, their formats, or what the parameters object should contain. The description doesn't compensate by clarifying these semantics, leaving both parameters undocumented and ambiguous in practice.

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 states the tool 'Execute[s] a processing algorithm with the given parameters,' which provides a basic verb+resource combination ('execute' + 'processing algorithm'). However, it's vague about what 'processing algorithm' means in this context (e.g., data transformation, analysis, etc.) and doesn't differentiate it from siblings like 'execute_code' or 'render_map,' which might involve similar processing concepts. It avoids tautology by not merely restating the name, but lacks specificity.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a loaded project or specific layers), exclusions, or comparisons to siblings like 'execute_code' (which might handle code execution) or 'render_map' (which might involve visual processing). Without such context, users must infer usage from the tool name alone, leading to potential misuse.

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