Create New App

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

With no annotations, the description carries full burden. It discloses that the tool scaffolds a Next.js project and includes specific components. The force parameter warns about overwriting existing files. However, it does not mention potential side effects like network downloads, dependency installation, or execution time. The behavioral disclosure is adequate but not exhaustive.

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 well-structured with front-loaded purpose: two sentences for what it does, then a list of features, then a usage guideline. The path parameter description is long but necessary. Overall, it is concise without wasted words.

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 no output schema, the description covers what the tool creates and includes usage considerations. It lacks detail on return values or success output, but the project contents are well described. With 4 parameters and no nested objects, the description provides sufficient context for an agent to understand the tool's scope.

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 100%, so baseline is 3. The description adds value by explaining what the resulting project includes, and the path parameter includes a concrete example and a warning about default behavior. The force parameter reinforces the safety warning. These details go beyond the schema's property descriptions.

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 creates a new production-ready app with specific features like auth, database, and payments. It lists the resulting project contents (dashboard, authentication, settings, etc.). This distinguishes it from sibling tools like varity_build or varity_deploy, which serve different purposes.

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 explicitly says when to use the tool: 'when a developer wants to start a new project, create an app, or scaffold something.' Additionally, the path parameter description provides critical usage guidance by instructing to always pass an absolute path and ask the user if unsure. However, it does not explicitly state when not to use it or list alternatives.

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