new_project

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the tool returns 'complete step-by-step setup instructions that you must follow exactly,' but does not reveal whether the tool has side effects (e.g., creates anything) or requires permissions. The lifecycle from this tool to actual project creation is unclear.

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?

Two sentences with front-loaded purpose and usage. While concise, the structure could be improved by separating usage scenarios from behavior, but overall it is efficient.

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 description explains that the tool returns instructions, but does not detail what those instructions contain or how the agent should proceed. Given no output schema, the agent may lack context for subsequent steps. The tool's role as a wizard starter is clear, but completeness is moderate.

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 tool has zero parameters, so the baseline is 4. The description adds value by explaining the tool's purpose and output, which compensates for the lack of parameter details.

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 identifies the tool as the initial entry point for project setup ('start a guided new Contextium project setup'). It distinguishes from siblings like 'create_project' and 'auto_project_setup' by emphasizing 'FIRST' and listing specific scenarios (set up project, create libraries, etc.).

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 explicitly states when to call this tool ('whenever a user wants to set up a new project...'), but does not explicitly mention when not to use it or directly name alternatives. However, the sibling list provides context, making the guideline clear enough.

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