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

Discloses wait time, auto-deploy, return of build_url, and real-time preview behavior. Annotations: readOnlyHint=false, openWorldHint=true, destructiveHint=false; description adds value beyond annotations and does not contradict them.

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?

Concise, front-loaded purpose, and every sentence adds value (usage, timing, checking behavior, sibling alternative). No fluff.

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 output schema exists and annotations provide safety profile, description fully covers when/when not, behavior, and return info. Nothing critical missing.

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 100%, so no parameter descriptions missing. The description adds context on prompt and context purpose indirectly, but not deeply.

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 states a specific verb and resource ('create a full website via Kleap') and differentiates from write_files, which is a sibling. It also describes the output (build_url).

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 when to use (user wants a complete hosted website/web app) and when not to (prefer write_files for full-site? Actually it says prefer this over write_files for full-site creation). It also clarifies not to block or poll check_task in widget clients, which is a strong when/when-not.

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