project_create

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

The description explicitly states the create action, which is consistent with the annotation readOnlyHint=false. It adds context about the workspace and initial content, but does not disclose potential side effects such as overwriting or behavior on name conflicts. Since annotations already cover mutability, the added context earns a slightly above baseline score.

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, concise sentence that starts with the action verb and includes essential context. There is no redundant or extraneous information, making it well-structured and efficient.

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?

While the description provides some context about the workspace and initial content, it does not explain the meaning of the required 'metadata' field or the optional 'metrics' and 'brief'. Given the schema's complexity and the creation context, the description is insufficient for an agent to fully understand what information to provide.

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 schema description coverage is 0%, and the description provides no information about the parameters 'brief', 'metrics', or 'metadata'. Since the schema is not self-explanatory for these parameters and the description completely omits them, it fails to compensate for the lack of schema-level 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 verb 'Create' and the resource 'project', while specifying the workspace and initial content ('Unicode UFO sources and technical glyphs'). This distinguishes it from sibling tools like project_open and project_update.

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 project creation but does not explicitly explain when to use this tool versus alternatives. There is no mention of exclusions or specific scenarios, leaving the usage guidance to inference.

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