helm_run_script

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

No annotations are provided, and the description only reveals the return structure. It does not disclose potential side effects, authentication requirements, or whether the run is synchronous or asynchronous, leaving significant behavioral gaps.

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?

Extremely concise: two sentences that front-load the action and include the return structure. No unnecessary words, every sentence 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?

For a simple tool with one parameter and no output schema, the description covers the basics. However, the lack of behavioral context (e.g., if it's destructive, how long it takes) makes it less complete for safe 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 description clarifies that 'name_or_id' can be either a script ID or name, which adds meaning beyond the schema's generic string type. With 0% schema description coverage, this compensation is valuable, though an example would improve 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 clearly states the action ('Run a script by id or name') and specifies the return value. It distinguishes from sibling tools like helm_list_scripts and helm_get_script, which have different purposes.

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 explicit guidance on when to use this tool versus alternatives. The purpose is implied, but lacking when-not or alternative recommendations for a contextual trigger.

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