remove_layer

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

The description indicates a destructive operation but does not disclose potential side effects, such as whether removal is permanent or if it affects dependent layers, annotations, or project state. With no annotations to clarify safety, this lack of transparency could lead to unintended consequences.

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, short sentence that is front-loaded with the key action and resource, making it easily parseable. Every word serves a purpose without 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?

While the description covers the basic purpose and parameter use, it lacks details on output, side effects, and usage context. Given no output schema or annotations, a more complete description would include notes on irreversible actions or required permissions to fully equip the agent.

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 clarifies that the layer_id parameter identifies the layer to be removed, which is not explicitly stated in the input schema (which only provides the parameter name and type). This adds minimal but necessary context for understanding how the parameter is used.

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 explicitly states the action 'Remove a layer from the project' and the method 'by its ID', making the tool's purpose clear. This verb-resource combination distinguishes it from sibling tools like add_raster_layer or get_layers, as removal is a distinct operation.

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, such as when to hide a layer instead of removing it. There are no prerequisites or conditions mentioned, leaving the agent without context for decision-making.

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