Start the site from a template

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

Discloses that the tool replaces site config and renders, adding detail beyond annotations (destructiveHint: true). No contradictions.

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: first covers action and effects, second gives after-use guidance. No redundant information.

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?

Given no output schema and moderate complexity, description covers purpose, usage, behavioral effects, and refinement steps. Adequate for an AI agent to understand and use the tool.

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 low (33%), but description adds context by listing what the tool sets (title, tagline, theme, sections, starter pages). However, it does not explain individual parameters like 'project' or the enum values beyond listing template types.

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?

Clearly states verb 'Seed' or 'Start' the website from a starter template (landing, docs, blog). Distinguishes from siblings like set_site/add_page by noting them as refinement tools.

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?

Explicitly says 'Replaces the current site config — use set_site/add_page to refine after', providing clear when-to-use and when-not-to-use guidance with alternative tools.

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