execute_command_enhanced

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

No annotations exist, so the description must fully disclose behavior. It mentions auto timeout extension and streaming but does not explain what these entail (e.g., automatic timeout extension while command runs, streaming of output). Missing details on blocking nature, return format, or side effects.

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 brief (one sentence), but at the cost of omitting critical information. It is under-specified rather than concise, and does not front-load essential details.

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?

With 14 parameters, no schema descriptions, and an output schema (unseen), the description is severely incomplete. It fails to provide sufficient context for correct invocation, especially given the complexity of the tool.

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 coverage is 0% (no parameter descriptions in the schema). The description only hints at two parameters (auto_extend_timeout, streaming_mode) without explaining their semantics, usage, or relationships to the 14 total parameters.

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 core action ('Execute a command') and highlights two features (auto timeout extension, streaming). However, it does not differentiate this tool from siblings like execute_command_async, which may also execute 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 on when to use this tool versus alternatives (e.g., execute_command_async for non-blocking execution, or basic execute_command). The description lacks context about appropriate use cases.

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