execute_command

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions execution 'in the background' and that it 'returns the output', but doesn't address critical aspects like security implications, permission requirements, timeout behavior, error handling, or whether commands persist across sessions. For a potentially dangerous shell execution tool, this is insufficient.

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 a single, efficient sentence that communicates the core functionality without waste. It's appropriately front-loaded with the main action and includes the key behavioral aspect (background execution) and outcome (return output). Every word serves a purpose.

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 with no annotations and no output schema, the description is inadequate. It doesn't explain what 'background exec window' means, doesn't address security concerns, doesn't describe output format or error conditions, and provides no guidance on appropriate usage. Given the potential danger of shell commands and the lack of structured safety information, this leaves significant gaps.

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 schema already documents both parameters thoroughly. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it mentions 'shell command' which aligns with the schema's 'command' description, but provides no additional context about command syntax, restrictions, or workspace implications.

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 action ('execute a shell command') and resource ('background exec window'), and specifies the outcome ('return the output'). It doesn't explicitly differentiate from siblings like 'start_process' or 'send_input', but the focus on shell commands and background execution provides reasonable distinction.

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 alternatives like 'start_process' or 'send_input'. The description mentions the 'background exec window' but doesn't explain what that means or when it's appropriate versus other execution methods. No prerequisites or exclusions are mentioned.

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