clasp_create

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

With no annotations provided, the description carries the full burden of disclosing side effects. It only states 'Create a new Google Apps Script project' without mentioning that this likely writes files locally (rootDir), may require authentication, or what happens with parentId. No behavioral context beyond the act of creation is given.

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 sentence with zero wasted words. It is front-loaded with the action and resource, making it highly scannable. No unnecessary elaboration distracts from the core purpose.

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 4 parameters and no output schema, yet the description provides no information about expected return values, side effects on the filesystem, or required setup (e.g., authentication). An agent would not know what the tool returns (e.g., project ID, success message) or how to use the created project afterward, leaving significant gaps.

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 100%, so the baseline is 3. The description adds no parameter-specific information beyond the schema; it does not explain how title, type, rootDir, or parentId relate to the project creation process. The schema already documents these fields adequately.

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 uses a specific verb ('Create') and resource ('Google Apps Script project'), clearly distinguishing it from sibling tools like clasp_clone or clasp_pull. It unambiguously states the tool's primary 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 implies usage for creating new projects, but provides no explicit guidance on when to use this tool versus alternatives (e.g., clasp_clone for copying an existing project). There are no exclusions or prerequisite conditions mentioned, leaving the agent to infer context.

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