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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description builds on that by defining the division of labor: the tool returns code, the coding agent installs it with its own tools, and the agent must relay placement options to the user. This is real behavioral context beyond the annotations, though it says nothing about the size or format of the returned snippet.

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 lead sentence is front-loaded and effective, but the head/body placement instruction is stated twice (once as guidance, again in the mandatory user-facing disclosure), and the platform list (Shopify, Wix, WordPress) is likewise repeated verbatim, padding the definition.

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 zero-parameter read tool with an output schema and full annotation coverage, the description supplies the essential operational context: check first, install once, where to place the snippet, platform alternatives, and who performs the install. An output schema exists so return-value details are rightly omitted.

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?

With zero parameters the baseline is 4, and the description usefully explains why there are none: the installation ID is account-based so no widget selection is needed. That preempts an agent wondering whether it must supply an account or widget identifier.

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?

"Get the JavaScript snippet that installs Chatway for the connected account" is a specific verb plus resource with clear scope. The follow-up clarifies the account-based installation ID so no widget selection is required, and the ordering instruction (check existing installation first) implicitly separates this from get-installation-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?

Gives strong when-to-use guidance: check for an existing installation before adding script_html, install only once, place in a shared layout. It also names alternatives (Chatway native app or plugin on Shopify, Wix, WordPress), though it never states an explicit case where this tool should not be called.

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