create_project

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'create a new project' and gives no indication of side effects, permissions required, return values, or any operational characteristics beyond the implied write action from the verb 'create'.

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 only a single sentence, but it is under-informative rather than appropriately sized. For an 8-parameter tool, one sentence that merely restates the name is too sparse, and the sentence does not earn its place by adding 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?

The tool has 8 parameters, no annotations, and no output schema, yet the description provides no context about the creation process, required steps, return values, or any operational detail. It is completely inadequate as a standalone description.

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 has 100% parameter description coverage, with each of the 8 parameters (ref, socid, title, status, date_end, date_start, description, budget_amount) having its own description. Since the schema fully documents parameters, the description's lack of param info is not a penalty, and the baseline score of 3 applies.

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 'Créer un nouveau projet' is a direct French translation of the tool name 'create_project', restating exactly what the name implies without adding specific detail. It is a tautology that offers no additional information about the tool's scope or what distinguishes it from other create_* tools.

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 any prerequisites or context. It is a bare statement with no situational advice.

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