Create a Quarto project

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

With no annotations, the description carries the full burden and does well: it discloses that the project is temporary, that the returned projectId is opaque and process-lifetime-bound, and that initial files are written. This is meaningful beyond the schema's static property descriptions.

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 dense sentences with no filler: the core action, the lifespan caveat, and the return value are front-loaded. Every phrase earns its place.

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 creation tool with five parameters fully described in the schema, the description covers the essential operational context: temporary lifecycle, initial file writes, and a projectId handle. It could optionally specify the response shape or cleanup semantics, but the described contract is sufficient 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 schema already documents every parameter. The description adds context around 'initial files' and return but does not need to restate parameter-level semantics.

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 states a specific verb ('Create'), a concrete resource ('Quarto project'), and clarifies behavior ('temporary', 'write initial files', returns an opaque projectId). This clearly distinguishes it from the sibling tools, which fetch defaults, render, inspect, or set defaults.

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?

The description communicates what the tool does and that it is for creating a project, but it does not explicitly state when to choose it over siblings or when not to use it. The intended use is implied rather than directly contrasted with alternatives.

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