helm_get_script

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

No annotations provided; description states 'Get' indicating read-only. However, no info on side effects, authentication, error handling (e.g., script not found), or return format. Adequate for simple retrieval but could add context.

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?

One short sentence with no filler. Every word adds value.

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 low complexity (1 param, no output schema), the description is functional but minimal. Lacks info about return contents (e.g., script code, metadata) and when to use vs other retrieval tools like helm_list_scripts.

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 coverage is 0%; description adds meaning by clarifying the parameter 'name_or_id' can be either a numeric id or a name. This goes beyond the schema's simple string type.

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?

Clear verb ('Get') and resource ('one script'), specifies identifiers (numeric id or name). Distinguishes from sibling tools like helm_list_scripts (list) and helm_run_script (execute).

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?

Implies usage when retrieving a single script by identifier, but no explicit when-to-use vs alternatives or when not to use. Lacks exclusions or conditions.

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