df_create_project

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

Annotations already indicate a non-read-only, non-idempotent, non-destructive operation. The description adds useful context that it writes to DataForge and that an initial version is automatically created. It does not disclose permissions, reversibility, or other side effects, but it goes slightly beyond the annotations.

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 three short sentences with no filler and the write warning is front-loaded. It is sparse but not padded, and every sentence carries at least some information.

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?

For a mutation tool with no output schema and minimal annotation detail, the description covers the key side effect (initial version creation) but omits expected response, prerequisites, and reversibility. It is minimally viable for a straightforward create operation, but not complete.

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 50%: color and idempotency_key are documented, but name and description are not. The tool description adds no parameter-level meaning and does not compensate for the undocumented parameters or explain the idempotency_key behavior.

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 states the specific verb and resource: 'Create a project.' The added note that an initial version is created clarifies scope. It does not explicitly distinguish this from siblings like df_create_version or df_update_project, but the resource is clear enough.

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?

There is no guidance on when to use this tool versus alternatives such as df_create_version or df_import_version_from_git. The description only restates the core action without context, triggers, or exclusions.

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