start_project

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

No annotations are provided, so the description must convey behavioral traits. It only states 'Initialize a new design project folder,' but does not disclose side effects (e.g., whether it overwrites existing projects), required permissions, or any limitations. This is insufficient for a creation action.

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 very concise, consisting of one line and an args section. It is front-loaded and avoids unnecessary detail. However, it could be slightly improved by integrating the args info more naturally, but overall it is appropriately sized.

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?

Despite the tool having an output schema (not detailed but present), the description does not explain return values or what happens after initialization. It lacks information on behavior if the project name already exists, where files are stored, or how to verify success. For a project initialization tool, this is incomplete.

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 single parameter 'project_name' has no schema description (0% coverage). The description adds an example ('e.g. 'burger_landing''), which provides some context but does not specify naming conventions, uniqueness constraints, or accepted formats. It adds marginal value over the parameter name alone.

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's purpose: 'Initialize a new design project folder.' The verb 'initialize' and the resource 'project folder' are specific. This distinguishes it from siblings like 'compile_project_drafts' or 'design_from_reference', which serve different functions.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no conditions for appropriate usage. It simply states what it does, leaving the agent without context for decision-making.

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