analyze_quarto_project

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds a meaningful behavioral constraint: the tool does not access the server filesystem and requires a path-only manifest, which affects how an agent must prepare inputs.

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 a single front-loaded sentence with no wasted words. The critical constraint about filesystem access is stated immediately alongside the input expectations.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a three-parameter tool with 0% schema description coverage, the description leaves metadata_config undocumented and does not distinguish this tool from analyze_quarto_document, leaving meaningful gaps.

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 0% across three parameters, so the description must carry parameter meaning. It loosely maps "Quarto YAML" to project_config and "path-only manifest" to file_manifest, but never mentions metadata_config and does not clarify formats, requiredness, or path 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 and resource: analyzing supplied Quarto YAML and a path-only manifest. It is clear what the tool does, but it does not differentiate itself from the sibling analyze_quarto_document, which likely operates on document-level input rather than project-level configuration.

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 implies the tool works only with supplied data ("no server filesystem access"), but it gives no explicit when-to-use guidance, no exclusions, and no alternative routing to analyze_quarto_document. An agent must infer usage conditions from the input mode alone.

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