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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation and non-destructive character are known. The description adds the scoping condition that domain is needed when multiple chatbots exist, which is useful operational context beyond the annotations. It does not describe side effects like what happens to existing links, but that is less critical given the annotations.

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 entire description is two short sentences. The main action is front-loaded and the conditional parameter guidance is stated in the second sentence, with no redundant words.

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 rename operation with two parameters and no output schema, the description covers the action and the key edge case (multiple chatbots requiring domain). It lacks any note about return values or effects on existing chat widgets, but these are not necessary given the tool's low complexity and annotation coverage. Overall it is nearly complete, falling just short of rich operational detail.

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%, with domain described as 'Which chatbot, when there is more than one' and new_name as 'New display name'. The description's phrase 'Pass the domain when the account has more than one' restates the schema's domain description without adding new meaning. Therefore it meets but does not exceed the baseline for high schema coverage.

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 opens with 'Rename a website chatbot', a specific verb and resource that clearly identifies the action. It distinguishes the tool from related siblings such as create_website_chatbot, delete_chatbot, and list_chatbots by the unique rename operation, though it does not explicitly reference an alternative.

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 provides one explicit conditional: 'Pass the domain when the account has more than one', which guides parameter usage when multiple chatbots exist. It does not, however, state when to prefer this tool over alternatives like update_chatbot_links or customize_chatbot_suggestions, leaving tool-selection guidance to inference from the name.

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