bdesign_project_create

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

Annotations already declare idempotentHint=false and destructiveHint=false, and the description aligns with these by indicating a new project is created (non-idempotent) and that creation is not destructive. The description adds the qualifier 'local' but provides no further behavioral details such as naming conflicts, overwriting behavior, or side effects beyond creation.

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 with no redundant words. It states the essential action and resource clearly, making it easy for an agent to parse quickly.

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 simple create operation with no output schema, the description conveys the core intent. However, it omits any mention of return value, success/error behavior, or potential confirmation steps, which could be relevant for an agent deciding how to handle the result. It is adequate but not fully complete for operational use.

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 input schema fully defines the single parameter 'name' with type string and min/max lengths, so schema coverage is 100%. The description does not add any extra semantic detail about the name parameter (e.g., uniqueness, formatting, default values), but because the schema is complete, the baseline score of 3 is appropriate.

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 'a new local BeatDesign project', distinguishing it from sibling tools like bdesign_project_list, bdesign_project_get, and bdesign_project_open. However, it does not explicitly differentiate itself from those siblings, relying on the phrase 'new local' to imply creation of a fresh project.

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, nor does it mention prerequisites, side effects, or typical use cases. An agent is left to infer that this is for creating projects, but there is no explicit statement about when to choose this over bdesign_project_open or bdesign_project_import.

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