expo_generate_project

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

With no annotations, the description carries the full burden of disclosing behavior. 'Generate Expo managed project' only implies scaffolding, but does not say whether files are created, whether it modifies the filesystem, whether an API key is needed, whether it contacts Expo services, or what side effects may occur.

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 short and front-loaded, with no wasted wording. However, it is under-specified for a tool with two parameters and no annotations; conciseness here crosses into insufficiency.

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 sparse schema, lack of annotations, and absence of an output schema, the description provides almost none of the context an agent needs: it does not explain what 'managed project' entails, what directory should contain, whether api_key is required for Expo services, or what the generated output looks like. Sibling tools like expo_setup_eas and rn_generate_project create ambiguity that the description does not resolve.

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 coverage is only 50%; directory is described in the schema but api_key is undefined there and not mentioned in the description. The description adds no meaning beyond the schema and fails to explain the role or optionality of api_key, which is critical given the schema provides no hint.

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?

Description identifies a concrete action (Generate) and a specific resource (Expo managed project). It is not a tautology and is easily distinguishable from sibling tools like expo_add_config or expo_setup_eas, though it does not carve out those distinctions explicitly.

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 given about when to use this tool versus alternatives such as rn_generate_project, expo_setup_eas, or expo_add_config. The intended context is vaguely implied by the name and resource, but the description does not state prerequisites, preferred scenarios, or exclusions.

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