ketan_run_bash_safe

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

With no annotations, the description carries the full burden and does excellent work: it discloses the pre-flight guard, atomic snapshot, workspace directory execution, and automatic rollback on non-zero exit or exception. This gives agents a full understanding of side effects and safety mechanisms.

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 well-structured with a numbered list of safety steps, an explicit preference note, and a concise args section. No unnecessary words; every sentence adds useful 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?

Given the tool's medium complexity and presence of an output schema, the description covers all critical behavioral aspects: protection mechanisms, rollback behavior, execution context, and parameter meanings. It is complete and self-contained.

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 description coverage is 0%, but the description fully compensates by explaining both parameters: 'command' is a shell command executed in the workspace directory, and 'timeout_seconds' is the max execution time with a default of 30. This adds meaning beyond the bare schema.

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 executes a shell command with protection, using a specific verb ('Execute') and resource ('shell command with FULL Ketan-OS protection'). It distinguishes itself from sibling tools by emphasizing the automatic snapshot/rollback safety features.

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 explicitly instructs to 'Always prefer this over raw bash for state-changing commands,' naming the alternative and indicating when this tool is appropriate. This is clear actionable guidance for tool selection.

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