preview_quire_project

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

With no annotations, the description carries the behavioral burden. It does disclose two meaningful side effects: generating HTML files and starting a local server on port 8080. However, it omits whether the server runs continuously, blocks the command, or needs to be stopped explicitly, which is important for a server-starting tool.

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 one tightly written sentence with no filler. It front-loads the core action ('Runs the Preview command') and adds the two most useful details: generated output and the local server port.

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?

The description covers the core action and even mentions the port, which is helpful. However, it lacks lifecycle context: the server presumably keeps running and should be stopped with stop_quire_preview, and there is no mention of what success looks like. Given the simple schema and sibling visibility, this is adequate but not fully 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 description coverage is 100%, so the baseline is 3. The description adds no parameter-level detail beyond the schema, but it does not need to because the schema already explains projectName and projectPath reasonably well.

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 action ('Runs the Preview command') and its concrete effects: generating HTML site files and starting a local server. It also gives a distinguishing detail ('Typically port 8080') that separates it from build_quire_project, which would not start a server.

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 does not say when to choose this tool over its siblings, nor does it mention stop_quire_preview as the way to halt the server it starts. The intended use is implied by the name and action, but no explicit guidance or exclusions are provided.

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