Create Project

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

Despite no annotations, descriptions detail name resolution behavior, case-insensitive exact match, AmbiguousMatch/NotFound errors, GitHub-link requirement, and return structure. Fully compensates for absence of annotations.

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?

Three sentences, each dense with essential information. Front-loads the main purpose, then details parameter constraints and behavior. No redundant or vague phrasing.

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?

Given 6 parameters (2 required), no output schema, the description covers required inputs, optional parameter logic, error scenarios, and return value. An agent has all needed context for correct invocation.

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?

Adds significant value beyond the input schema: explains mutual exclusivity of teamUuid/teamName and repoUuid/repoName, backend resolution behavior, and return fields. Schema coverage is 100% but description enriches understanding.

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 explicitly states 'Create a new DebuggAI project' and lists required fields (name, platform) and optional parameters. It clearly distinguishes this creation tool from siblings like delete_project, update_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?

Provides clear context for using team and repo parameters (UUID vs name, case-insensitive matching, ambiguity/not-found errors). Does not explicitly mention when to avoid using this tool, but the creation purpose is unambiguous.

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