Create Live Agent Chat Button

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), the description adds behavioral details such as routing type behavior, optional bot handling, and the embedding follow-up. This provides useful context without contradicting any 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 description is well-structured: a clear purpose sentence, a concise parameter list, and a follow-up note about embedding. It is slightly verbose but each part contributes useful information, with the parameter list serving as a quick reference despite schema redundancy.

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?

Given 10 parameters, no output schema, and minimal annotations beyond safety hints, the description should clarify return values and prerequisites. It covers parameter semantics and the embedding step, but omits expected return data and has the routingType ambiguity, leaving it incomplete.

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 description adds explanations for many parameters, but it misrepresents routingType by listing 'Choice' and 'Queue' while the schema enum defines 'Queue' and 'Bot'. This inconsistency undermines the parameter guidance and could lead an agent to pass an invalid value. Other parameter explanations are helpful but offset by this error.

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 tool creates a Live Chat button (LiveChatButton) that can be embedded on websites to start chat sessions. This specific verb+resource distinguishes it from sibling create tools, and the mention of sf_create_embedded_service further contextualizes its role.

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 clear usage context by explaining the routingType options and pointing to sf_create_embedded_service as the next step after creation. It does not explicitly exclude alternatives, but the workflow guidance is sufficient for an agent to know when to use this tool.

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