execute_with_auto_retrieve

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

With no annotations, the description carries the full behavioral burden, and it does disclose that execution blocks and that output is auto-retrieved. It says nothing about timeouts, exit-code or error behavior, output truncation, or side effects of arbitrary command execution. Genuinely useful context, but significant gaps remain for a shell-execution tool.

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?

Two tight sentences with zero waste: the core behavior and the synchronous-output promise come first, then the routing rule against the alternative. Nothing is redundant or buried.

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 two-parameter, fully schema-documented command runner with no output schema, the description covers what it does, how it returns results, and when to prefer it. The missing pieces — timeout behavior and error/exit-code reporting — are modest but real for a command executor.

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% and both parameters (command, working_directory) are documented in the schema itself. The description adds no information about command syntax, shell used, or working-directory defaults, so baseline 3 applies.

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 states a specific verb and behavior: executes a command, waits for it, and returns its output. The blocking/auto-retrieve semantic is a genuine differentiator. However, it does not distinguish itself from close siblings like execute_command, execute_with_streaming, or execute_and_parse, which an agent would also plausibly reach for.

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?

It gives a clear selection rule — 'preferred for quick commands that don't need a visible terminal tab' — and explicitly names open_terminal_tab as the alternative for long-running processes. It stops short of addressing the arguably more confusable siblings (execute_command, execute_with_streaming), leaving that comparison to inference.

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