create_presentation

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

With no annotations provided, the description carries the full burden. It discloses the created files and the npm install side effect, including the install=false override, which is useful. However, it does not mention behavior if the target folder already exists, potential overwrites, or the return value, leaving some uncertainty.

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, front-loaded with the verb and resource, no fluff. The install behavior is clearly appended as a conditional, making it easy to scan.

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 tool is a simple scaffold operation with complete schema documentation; the description covers the main action and side effects. Gaps include no output schema or return value details and no mention of error cases, but the essential invocation context is present.

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?

The schema provides complete coverage for all four parameters, giving a baseline of 3. The description adds some context by clarifying that install controls npm install and that the tool scaffolds a folder with slides.md and package.json, but it doesn't add significant meaning beyond the schema.

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 uses a specific verb ('scaffold') plus resource ('new Slidev presentation') and details what is created (folder + slides.md + package.json), clearly distinguishing it from the sibling tools that list, start, stop, select, or call presentations.

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 when to use the tool—when a new Slidev presentation is needed—by specifying the scaffolding behavior. It doesn't explicitly exclude alternatives or state when not to use, but the distinct creation purpose provides clear context relative to siblings.

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