helm_delete_service

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

With no annotations provided, the description must convey behavioral traits. It mentions the side effect of stopping before deletion, which is useful. However, it does not disclose whether deletion is irreversible, require authentication, or have other consequences. For a destructive operation, more explicit transparency would be beneficial.

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 extremely concise—one sentence with no filler. It is front-loaded with the action and includes a parenthetical note for the side effect. Every word earns its place.

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 simplicity of the tool (one parameter, no output schema, destructive action), the description covers all necessary aspects: what it does, how to identify the service, and the side effect. No additional information is needed for correct invocation.

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 single parameter 'name_or_id' is described as accepting either a service id or name, adding meaning beyond the schema's 'Name Or Id' title. Since schema description coverage is 0%, this clarification is valuable and helps the agent correctly identify the service.

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 tool deletes a service, specifying that it stops the service first if running. The verb 'delete' is specific to the resource 'service', and it distinguishes well from siblings like helm_stop_service (which only stops) and helm_delete_stack (deletes a stack).

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 implicitly guides usage by contrasting with stop functionality, but it does not explicitly state when to use this tool vs alternatives (e.g., 'Use helm_stop_service if you only want to stop it'). Nonetheless, the context is clear enough for an agent to infer the appropriate scenario.

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