executeCommand

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

No annotations are provided, so the description carries full responsibility. It mentions 'safely run' but gives no details on safety mechanisms, restrictions, side effects, or output behavior (stdout/stderr). The agent lacks critical behavioral context.

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 two efficient sentences: the first defines the tool's action with examples, the second provides usage context. No superfluous information.

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?

The tool has moderate complexity with two well-documented parameters and no output schema. The description covers purpose and usage but omits crucial details: return output (stdout/stderr with exit code), execution environment (project root directory), and blocking nature. These gaps reduce completeness.

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?

Both parameters have descriptions in the schema (100% coverage). The description adds example commands (npm test, git status, npm run build) which help ground the usage, but does not add additional semantic depth beyond what the schema already provides.

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 runs shell commands safely on the local terminal, gives concrete examples (npm test, git status, npm run build), and distinguishes from sibling tools that handle file operations, search, or task dispatch.

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 specifies when to use the tool: after code modifications to verify errors, install dependencies, or run builds. It does not explicitly mention alternatives or exclusions, but the provided contexts cover common use cases.

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