speckle_project_create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Create', which implies a write operation, but does not mention authentication requirements, reversibility, side effects, or what happens on creation. The description adds little beyond the verb itself.

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, front-loaded sentence that clearly states the action and purpose with no wasted words. It is easy to parse and immediately conveys the tool's role.

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 a simple schema and an output schema, but the description is too sparse for a create operation with no annotations. It omits parameter details, usage guidance, and behavioral context, making it insufficient for an agent to correctly select and invoke the tool.

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% and the description provides no explanation of the parameters (name, visibility, description). The agent receives no guidance on parameter formats, allowed values, or their meanings, leaving the agent to rely solely on property names.

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 creates a new Speckle project, with a specific resource (project) and a purpose clause ('to organize models shared across your team'). This distinguishes it from sibling tools like speckle_model_create, which creates models, and speckle_projects_list/details which are read operations.

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 a use case but does not explicitly state when to use this tool over alternatives. It mentions 'organize models shared across your team,' which provides context, but lacks explicit guidance on when not to use it or how it differs from speckle_model_create.

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