run_workspace_command

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

With no annotations, the description carries the full burden, and it does disclose the key trait that the tool is read-only and restricted to a fixed command set. It says nothing about error behavior for unknown commands, permission requirements, or whether directory traversal outside the workspace is blocked, which are the traits an agent would want before calling a command executor.

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?

A single tight sentence with the constraint front-loaded and zero filler; the semicolon efficiently separates the capability from its restriction. It is efficient, though its brevity contributes to the parameter and behavior gaps noted elsewhere.

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 command-execution tool with no annotations, no output schema, and zero schema description coverage, the definition is thin. An agent cannot learn from it what the output of each command looks like or how 'directory' scopes execution, both of which matter for correct invocation.

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 0%, so the description must supply parameter meaning, but it says nothing about either parameter. The 'directory' parameter, its default of '.', and whether it is relative to the workspace root are entirely undocumented, and the description adds no meaning beyond the enum already present in the schema for 'command'.

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?

States a specific verb and resource ('run a limited read-only command') and immediately bounds scope with 'no shell or arbitrary programs', which tells the agent this is a constrained inspection tool rather than a general executor. It does not name any sibling such as list_files or read_file, so the differentiation from those is left to inference.

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 'no shell or arbitrary programs' clause is a useful exclusion that rules out pipelines, redirection, and custom binaries, implying usage only for vetted inspection commands. However, there is no positive guidance on when to prefer this over list_files or read_file for the same information, and no mention of prerequisites or working-directory expectations.

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