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

Annotations already disclose that this is a non-read-only, idempotent, destructive, open-world operation. The description adds useful context by equating on:true with the dashboard's Enable embed and by stating that messaging channels are unaffected, though it does not explain the consequences of turning the widget off.

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 definition is two sentences, front-loaded with the core action and immediately followed by the important scope caveat. There is no filler or repetition.

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 simple two-parameter mutation with rich annotations and no output schema, the description gives enough context to call the tool correctly. A minor gap remains around the destructive implication of disabling the widget, but the destructiveHint annotation already signals that risk.

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 only 50%, but the description compensates well for the boolean parameter by explaining exactly what on:true and on:false mean. The agent_id parameter is documented in the schema as coming from list_agents, so both parameters are sufficiently covered.

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: turning the agent's chat widget on the business website on or off. It also clarifies scope by saying messaging channels are not changed, which helps an agent distinguish this tool from broader channel-management work.

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 maps on:true to the dashboard's Enable embed action and on:false to disabling it, and explicitly excludes Telegram/WhatsApp management. It does not give a full decision rule for when to use this tool versus the dashboard for widget management, but the usage context is clear.

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