shell_execute

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

No annotations are provided, so the description must disclose behavior. It does state allowed commands, but the incomplete 'Allowed patterns:' and lack of information about error handling, permissions, or side effects leave important behavioral context unknown. For a shell execution tool, this is a significant gap.

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 brief but not well-structured: the second sentence is cut off mid-phrase ('Allowed patterns: '), making it appear as a formatting artifact rather than concise prose. It should either complete the pattern list or remove the line.

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 lack of annotations, output schema, and sibling context, the description is incomplete for a security-sensitive tool. It fails to mention what happens with disallowed commands, whether stdin is always supported, timeout semantics, or any examples of valid invocations.

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?

All parameters have descriptions in the input schema (100% coverage), so the description adds no additional parameter semantics. The mention of 'Allowed commands' relates to possible values for the 'command' array but does not specify format or constraints beyond the 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 primary action 'Execute a shell command' and enumerates a specific allowlist ('Allowed commands: echo, cat, ls'), which differentiates it from arbitrary shell executors. However, the 'Allowed patterns:' line is incomplete, slightly muddying the exact scope.

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 is provided about when to choose this tool over alternatives, and there are no sibling tools listed. The description only states what commands are allowed, not when execution is appropriate. Since the tool name suggests a general shell executor, the description should clarify that it's restricted to safe read-only commands like echo, cat, and ls.

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