install_deps

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

The description reveals the underlying command but not the side effects. It does not disclose that installation typically modifies the project's manifest and lockfile, requires network access, or may fail when the project path is invalid. Since no annotations are provided, the description carries the full burden of behavioral disclosure and only restates that dependencies will be installed.

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 a single, front-loaded sentence with no filler or repetition beyond the name. It is concise, though some of that brevity comes at the cost of missing behavioral and parameter context.

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 two parameters, no annotations, and no output schema, the description is too thin. It does not provide prerequisites, project path semantics, side effects, or error behavior, leaving an agent without enough information to invoke it reliably.

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 schema only provides types and required status. The description suggests that 'packages' refers to dependencies to install, but it does not clarify that these are package names for npx expo install, nor does it explain the meaning or default of 'projectPath'.

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 ('Install dependencies') and the mechanism ('using npx expo install'), so an agent can identify what operation the tool performs. It does not explicitly differentiate from sibling tools, but none of the listed siblings appear to perform package installation, so this is not a practical concern.

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 is provided about when to use this tool versus alternatives or what preconditions are needed. It does not mention that this is intended for Expo/React Native projects, whether it modifies package.json, or when agents should choose a different tool such as manage_bundler.

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