shell_execute

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

Annotations are absent, so the description must disclose behavior. It states default/max timeout and output cap, and lists allowed commands. However, it does not explain what happens on timeout or disallowed commands, or mention return format or error handling, leaving 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?

The description is concise (3 lines), front-loaded with the core action, and each sentence provides distinct information (action, allowed commands, constraints). No unnecessary text.

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 execution tool, critical context is missing: no mention of sandboxing, shell used, environment variables, or return value format (stdout/stderr). Despite listing constraints, it fails to provide a complete picture of behavior and output.

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%, so baseline is 3. The description adds context like default timeout and output cap, but these are execution constraints, not parameter-level details. It does not clarify parameter behavior beyond the schema descriptions.

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 starts with 'Execute a shell command' which is a clear verb-resource pair. It lists allowed commands, providing specificity and distinguishing scope. No sibling tools exist, so differentiation is not applicable.

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 description lists allowed commands and timeout limits, guiding the agent on permissible usage. Without sibling tools, explicit alternatives are unnecessary; the provided constraints serve as implicit usage guidance.

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