Create Project

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

Discloses key behavioral traits: auto-creates a tag, returns conflict on duplicate slug, and requires confirmation. No annotations exist, so description carries full burden; it does well.

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?

Concise with 4-5 sentences, each contributing unique value: purpose, side effects, usage guidance, examples, confirmation. Well-structured and front-loaded.

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?

With no output schema and 3 parameters, description covers purpose, side effects, usage triggers, and confirmation behavior. Missing return value details but adequate for the tool's simplicity.

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 100%, so baseline 3. Description adds context that 'name' leads to slug-based conflict, but does not elaborate on 'status' or 'description' beyond schema. Meets minimum but adds limited extra meaning.

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?

Clearly states 'Register a new project' with specific verb and resource. Distinguishes from sibling tools like create_tag or create_task by focusing on project creation. Includes side effects and conflict behavior.

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?

Provides explicit when-to-use scenarios with example triggers ('I'm starting a new project called X') and instruction to always confirm. Does not explicitly state when-not-to-use, but conflict description implies pre-existing projects are not suitable.

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