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

The description adds meaningful behavior beyond annotations: it discloses that the tool crawls the website automatically, imposes a 2-per-account limit, and only requires website_url. Since annotations are minimal (readOnlyHint=false, destructiveHint=false), this context helps the agent anticipate side effects and constraints.

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 carry all the essential information: what it does, when to use it, a key account constraint, and the required parameter. Information is front-loaded and nothing is redundant.

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?

The description explains the return value (embed snippet), the required input, and the account limit, which is solid for a creation tool with no output schema. It does not mention failure modes or behavior if the site cannot be crawled, but the core information an agent needs to invoke it correctly is present.

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 the baseline is 3. The description adds no per-parameter semantics beyond what the schema already provides; it only reinforces that website_url is required. This is adequate but does not elevate the dimension.

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 an AI chatbot widget') and immediately clarifies its scope: it crawls the site, builds a knowledge base, and returns an embed snippet. This clearly distinguishes it from sibling tools like list_chatbots, rename_chatbot, or customize_chatbot_suggestions.

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?

Explicit trigger phrases are provided ('website chatbot', 'chat widget', 'AI assistant on their site', 'put Dottie on my website'), which gives strong when-to-use guidance. It does not explicitly name alternative tools or state when not to use it, so it falls just short of a 5.

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