Delete Field

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

The destructiveHint annotation already signals the tool modifies data. The description adds no further behavioral disclosure (e.g., irreversibility, impact on related data, permissions needed). Beyond annotations, it offers no additional 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?

The description is a single sentence with no fluff. However, it is so brief that it omits potentially useful context. It earns a 4 for conciseness but loses 1 for being under-specified.

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 no output schema and 2 required parameters, the description lacks essential context about the destructive nature of the operation and what happens to the data. It does not compensate for the missing structured details.

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%. The description does not explain the parameters (layer_id, field_name) beyond listing them in the schema. It adds no semantic value or domain context for the parameters.

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 'Delete a field from a vector layer,' specifying the action (delete), resource (field), and context (vector layer). It distinguishes from sibling tools like add_field or rename_field.

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?

No guidance on when to use this tool versus alternatives (e.g., delete_features, remove_layer), nor any prerequisites or use cases. The purpose is implied but not explicitly contextualized among siblings.

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