publish_site

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

Annotations set destructiveHint: true and idempotentHint: true. The description adds behavioral details by explaining the first publish sets up external infrastructure (GitHub, Vercel) and subsequent calls are rebuilds, adding context beyond the annotations. However, it doesn't elaborate on what destruction entails.

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, no redundancy, directly front-loads the core purpose. Every clause adds value, making it highly concise and well-structured.

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 the simple single parameter, no output schema, and annotations covering key hints, the description adequately covers behavioral nuances (first vs subsequent call behavior) and external dependencies, completing the context.

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 sole parameter siteId has a schema description indicating its source ('from list_user_sites or get_generation_status'), providing full schema coverage. The tool description does not add further parameter meaning, so baseline of 3 is appropriate.

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 clearly states the tool's action: 'Publish a site to production at slug.the-template-vault.com.' It distinguishes between first publish (wires up GitHub repo + Vercel project) and subsequent calls (triggers Vercel rebuild), differentiating from siblings like generate_site and get_generation_status.

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 (to publish a site) but provides no explicit guidance on prerequisites, such as requiring a generated site first, or when not to use it. It does not mention alternatives like generate_site vs publish_site.

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