ds_create_project

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

With no annotations, the description must disclose behavioral traits. It only states 'Create a new project,' which implies a write operation but omits important details like error handling, naming constraints, or consequences of creating a project with an existing name.

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 brief and front-loaded with the primary action. The args list is clearly structured, though it largely repeats schema information, which slightly reduces its value.

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 simple tool and lack of output schema, the description barely covers essential context. It does not mention what the return value is, whether any dependencies exist, or how this tool fits with the abundant sibling tools, leaving the agent under-informed.

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 0%, so the description must compensate. The listed args 'name' and 'description' add only a modicum of meaning ('Project name', 'Optional description') beyond the schema's titles and default, but they do not clarify formats, constraints, or semantics that would aid correct invocation.

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 explicitly states 'Create a new project,' which is a clear verb-resource pairing that distinguishes the tool from sibling tools like 'ds_delete_project' and 'ds_rename_project.' However, it does not elaborate on what a project is in this context, limiting full clarity.

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 or when to prefer an alternative. There is no mention of prerequisites, exclusions, or how this differs from other create-related tools such as 'ds_create_workflow'.

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