ado_create_project

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

Discloses async behavior and OperationReference return beyond empty annotations. Also explains template resolution logic. Could add more on permissions or failure modes, but sufficient.

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 cover essential info without waste. Front-loaded with action and key behavior.

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?

Adequate for a create tool with 6 params and no output schema. Covers async nature and template resolution, but missing constraints like uniqueness or permissions.

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 83%, so baseline is 3. Description adds useful context on processTemplate resolution (by name when ID not given), enhancing parameter 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?

Clearly states 'Create a new project' with specific verb and resource. Notes async operation and return type, distinguishing it from sibling tools like update or get.

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?

Implied usage for creating projects, but no explicit when-not or alternatives provided. Lacks guidance on choosing between processTemplate and processTemplateId.

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