run_command

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

Annotations only declare readOnlyHint=false, so the description carries the burden and does add the useful constraint that commands are limited to PROJECT_MCP_ALLOWED_COMMANDS prefixes. That is real behavioral context (a security boundary), but it omits blocking/timeout behavior, shell semantics, and what 'or default' actually permits.

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 short sentences, front-loaded with the core action and zero padding. The trailing 'or default' clause is slightly cryptic but overall it is tight and efficient.

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?

This is a generic command-execution tool with a destructiveHint-adjacent annotation (readOnlyHint=false), 0% param coverage, and only an opaque reference to an env-var allowlist. Output schema covers returns, but the description leaves working-dir vs project_path semantics, env behavior, and execution safety unexplained.

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 compensate and it does not. It hints that a command runs in a project dir (loosely explaining project_path), but never explains the 'command' format or what the 'env' parameter does.

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 ('Run') and resource ('a command in project dir'), so the core action is immediately clear. However, it does nothing to distinguish itself from siblings like run_tests or deploy, nor to signal its generic shell-execution scope beyond the word 'command'.

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 names an allowed-prefix constraint but gives no when-to-use guidance and no comparison to alternative execution tools such as run_tests or deploy. An agent gets no signal about when this generic runner is preferable to the more specific siblings.

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