run_shell_command

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

Description hints at policy enforcement but does not detail behavioral traits such as permissions, side effects, or restrictions. No annotations provided to compensate; for a shell command tool, this is insufficient.

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?

Single sentence, 10 words, no unnecessary content. Efficient and front-loaded.

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 shell command execution tool, description lacks detail on output format, error handling, and what 'narrow' means. No output schema, no annotations; context is incomplete.

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 100% for the 'command' parameter, but its description 'Command line to evaluate.' is minimal. Tool description adds 'narrow' and 'agent-sudo' but does not enrich parameter semantics beyond baseline.

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?

Description clearly states verb 'Run', resource 'narrow local shell command', and context 'through agent-sudo policy enforcement'. Distinguishes from siblings (get_runtime_context, read_file, write_file) which are not shell execution.

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 like read_file or write_file. Does not mention limitations or when not to use.

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