run_shell

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds meaningful context the annotations cannot: commands execute as the user 'Jashan' from his home folder, and sudo is unavailable. It does not explain output formatting or error behavior, so it is good but not exhaustive.

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?

Front-loaded with purpose and routing in the first two sentences, then environment caveats, then a clean args block. Every sentence earns its place with no filler.

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 an arbitrary shell-execution tool with no output schema and 0% param coverage, the description supplies the identity/environment context, the sudo limitation, timeout default, and invocation examples. The main remaining gap is describing how output and errors are returned, which is minor since the description says to read the output directly.

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%, so the description carries the parameter burden and does so well: it gives three concrete command examples ('ls ~/Downloads', 'git -C ~/x status', 'brew list | head') and explains timeout as 'Seconds to allow before giving up (default 60)'. This compensates for the bare schema, though it could note the working-directory assumption more explicitly.

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?

States a specific verb and resource ('Run a shell command and read its output') and then positions it against the entire sibling set with 'The way to do anything with no dedicated tool.' An agent can immediately tell this is the catch-all escape hatch rather than any of the specialized tools.

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 line 'the way to do anything with no dedicated tool' is an effective when-to-use rule, implying dedicated siblings should be preferred. It also warns that sudo won't work, which is a real usage constraint. It stops short of naming alternatives explicitly, so it is clear context rather than a full when/when-not/alternatives breakdown.

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