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

The description explicitly warns that the operation overwrites current instructions and affects every visitor's chatbot experience. This goes beyond the destructiveHint annotation by explaining the real-world impact and the need for user confirmation.

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 three concise sentences, front-loaded with the action and key warning. It contains no fluff or redundant phrasing, making it easy for an agent to parse and act on.

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 is complete enough for a simple two-parameter update tool: it states the action, the side effect, the prerequisite read, and the required user confirmation. No output schema exists, and the description does not need to elaborate further.

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 schema already provides full descriptions for both parameters, including the optional website_id behavior. The description adds no additional parameter-level detail beyond what the schema covers, so the baseline score of 3 is appropriate.

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 action ('Replace'), the resource ('one website's AI instructions'), and the effect ('changes how the live chatbot answers every visitor'). It is unambiguous and distinct from the related get_ai_instructions tool.

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 explicitly instructs to read the current instructions with get_ai_instructions first and to show the user what will change before calling. This provides clear prerequisite and safe-usage guidance, leaving no ambiguity about the intended workflow.

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