Install dependencies

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

With no annotations, the description must convey behavior and safety. It states 'Run npm install' but does not disclose that this modifies package files, may access the network, or could have side effects. The agent is left unaware of the tool's impact.

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 concise—one short sentence—with no fluff. However, it is terse to the point of brevity, though that does keep it easy to parse. The structure is fine, but it sacrifices necessary detail 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?

Given the simple one-parameter tool, the description still omits critical context: what 'app' refers to, what installation entails, and expected outcomes. Without output schema or richer description, the agent has insufficient information 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?

The schema has one required parameter 'app' with zero description coverage. The description does not explain what 'app' represents (e.g., an ID or path) or how to obtain it, so the agent cannot correctly construct the argument.

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 action 'Run npm install' and the target context 'in the app directory.', which is specific both in verb and resource. It is distinct from sibling tools like read_file or deploy, so an agent can immediately understand its function.

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 gives no indication of when to use this tool versus alternatives such as create_app or set_env. It lacks any context about prerequisites, when dependency installation is needed, or that it should be called after app creation.

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