create_project

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

Discloses mutation behavior, session authentication with CSRF protection (Origin/Referer), and plan-based restrictions. With no annotations provided, the description fully covers behavioral traits.

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 single sentence that first states the core purpose, then efficiently adds plan details and auth requirements. No wasted words.

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?

Fully covers all relevant context: action, parameters, plan restrictions, and authentication behavior. No output schema needed for this mutation tool; description is complete.

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% with good descriptions. The description adds clarity by explaining 'name = display name' and 'slug = a short URL-safe identifier', but mostly echoes schema info. Slight added value over schema.

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 the action 'Create a new project' and specifies the HTTP method. Distinguishes from sibling create tools by focusing on project-specific details like plan limitations.

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 usage context including plan caps (Pro 5, Team unlimited, Free cannot create) and authentication requirements. This helps the agent decide when to use this tool and when not to.

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