delete_feature

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that multiple indices are deleted in reverse order automatically, but it does not state whether deletion is irreversible, whether it requires confirmation, or what happens on invalid indices.

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 short and front-loaded: the core action appears first, followed by the discovery hint and then the parameter format. Every sentence adds useful invocation information.

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 gives enough to call the tool correctly, including the required index format and reverse-order deletion behavior. Because an output schema exists, return-value details are not required, though the lack of safety/irreversibility context is a minor gap for a destructive operation.

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 schema only gives a bare string type for the required indices parameter, so the description meaningfully compensates by explaining the comma-separated format and giving an example. The instance parameter is documented in the schema itself, so the description does not need to repeat it.

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 a specific verb and resource: deleting one or more features by index. It also distinguishes the target from related operations by specifying feature indices and pointing to list_features() for discovery.

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 gives clear usage context by telling the agent to use list_features() to find valid indices. It does not, however, explain when to delete versus suppress a feature or mention prerequisites/exclusions.

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