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

The description discloses asynchronous behavior (returns a job handle), the need to share the URL before waiting, the polling requirement, and the default preview behavior for empty templates. Since annotations are all false (no readOnly, idempotent, etc.), this fills the gap with essential behavioral context.

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?

The description is longer than typical but each sentence contributes value, starting with the core action, then returns, usage instructions, and template specifics. It is logically structured and front-loaded with the primary purpose.

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?

For a tool with async job creation, liveUrl, and preview generation, the description covers all necessary context: how to use the URL, polling, and template edge cases. The output schema likely handles return structure, and the description leaves no major gaps 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful context beyond the schema: it explains that template=empty skips preview by default and that generatePreview overrides it, adding nuance not present in the schema's property descriptions.

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 opens with 'Create a project from a template', clearly stating the verb and resource. It then details the return values (liveUrl, job handle) and distinguishes from sibling tools like project_update or project_delete by focusing on creation from a template.

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 post-call instructions: share the liveUrl immediately as a Markdown link, mention sign-in, poll job_get, and explains when to expect the first revision. It also clarifies the template=empty behavior and how generatePreview overrides it, giving an agent clear guidance on when and how to use the tool.

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