vibekit_remove_domain

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action ('Remove a custom domain from an app') without noting whether the removal is permanent, whether it affects live traffic, or if any prerequisites exist. This is minimal disclosure for a destructive action.

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, concise sentence that immediately communicates the tool's purpose. There is no wasted content, and the key information is 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?

For a tool with a single, well-documented parameter and no output schema, the description is minimally adequate. However, it lacks any mention of side effects, return values, or behavioral consequences (e.g., whether removal disconnects the domain immediately). Given the simplicity, a middle score is appropriate.

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 only parameter (appId) is fully described in the schema as 'App ID or subdomain slug', which provides complete semantic coverage. The tool description adds no additional meaning or context for the parameter, so it does not exceed the schema baseline.

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 removes a custom domain from an app, using a specific verb ('Remove') and resource ('custom domain'). This distinguishes it from the sibling vibekit_add_domain, which performs the inverse operation.

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 provides no explicit guidance on when to use this tool versus alternatives like vibekit_add_domain. Usage is implied by the tool name and the presence of an inverse sibling, but no explicit when/when-not criteria are given.

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