efs_exec

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions returning stdout/stderr but does not disclose important traits such as error handling (e.g., behavior on non-zero exit codes), environment context, security restrictions, or side effects. For a shell execution tool, this is a significant transparency 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 extremely concise: one sentence states the core action and output, followed by a brief parameter summary. Every word earns its place, and the crucial verb is front-loaded.

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 incomplete. It does not specify the return structure (e.g., whether stdout/stderr are separate fields), exit code behavior, or whether the command runs in a specific shell. The tool's complexity demands more context than just 'return stdout/stderr'.

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%, with each parameter already well-described in the schema (command, cwd, timeout). The description adds no extra semantics beyond restating the parameter names and notes like 'default 30000', which is already in the schema. Baseline 3 is appropriate because the schema handles the burden.

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 tool's purpose: 'Execute a shell command and return stdout/stderr.' This uses a specific verb (execute) and resource (shell command), distinguishing it from sibling tools like efs_read and efs_write. The parameter list further clarifies 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?

The description implies usage (e.g., you need to run a shell command), but provides no explicit guidance on when to use this tool versus alternatives like efs_python or process_tool. There are no exclusions or alternative tools mentioned, leaving the context implied rather than stated.

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