execute_shell

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

No annotations are provided, and the description fails to disclose important behavioral traits for a shell execution tool, such as potential side effects, security implications, or required permissions. The phrase 'multi-level security' is vague and does not compensate for the lack of transparency.

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 (one sentence) but fails to front-load critical information or provide a structured breakdown. While brevity is positive, the lack of structure reduces its helpfulness for an AI agent.

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 complexity (9 parameters, 100% schema coverage, no output schema, no annotations), the description should address error handling, output format, and side effects. It does not, leaving the agent uninformed about return behavior and potential risks.

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 100%, so the baseline is 3. The description adds minimal value beyond the schema by introducing the securityLevel parameter implicitly, but it does not clarify parameter semantics beyond the schema definitions.

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 'Execute shell commands with multi-level security' clearly states the verb (execute) and resource (shell commands), and adds a distinguishing feature (multi-level security) that separates it from similar tools like 'shell'. However, it could be more specific about the scope of commands.

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 on when to use this tool versus its siblings, such as 'shell' or other command-execution tools. The description does not mention prerequisites, alternatives, or context where this tool is appropriate.

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