vibie_create_site

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

Discloses auto-creation of a .vibie/site.json marker and the permanent URL pattern. However, it does not mention that the folder must contain index.html or a single HTML file, which is a required input detail from the schema. No annotations exist, so description carries full burden.

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?

Four sentences, each serving a distinct purpose: core action, usage context, hosting detail, side effect. No unnecessary words, well front-loaded.

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?

No output schema, yet description fails to mention what the tool returns (e.g., site ID, URL). Important for an agent to know the result. Also missing error conditions or permissions. Incomplete for a creation 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 description coverage is 100%, so baseline is 3. The description reinforces the 'folder' parameter with 'upload a local folder' but adds no new meaning beyond the schema's parameter descriptions.

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 'Create a NEW Vibie site by uploading a local folder', using a specific verb and resource. It distinguishes from siblings (get, list, update) by focusing exclusively on creation.

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 tells when to use: 'Use this when the user wants to publish a brand new site, or when no .vibie/site.json marker exists in the folder.' This gives clear conditions and implies alternatives (e.g., update_site for existing markers).

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