contacts_start_chat

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says only 'Start a chat contact' and omits details such as permissions, side effects, return behavior, or async nature. This is a significant gap for a tool that initiates a contact.

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 a single sentence that wastes no words and contains no redundant information. It is appropriately front-loaded, though its extreme brevity limits the information actually conveyed.

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 the tool has four parameters and no annotations, the description is grossly incomplete. It provides no context about prerequisites, the role of the contact flow, participant display name, or what the output represents. The entire description is three words, which is inadequate for a tool of this complexity.

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 description coverage is 0%, so the description must compensate by explaining parameter meaning. It does not mention instance_id, contact_flow_id, participant_display_name, or attributes, leaving all four parameters semantically undefined beyond their names.

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 'Start a chat contact' uses a specific verb ('start') and resource ('chat contact'), clearly distinguishing it from sibling tools like contacts_start_outbound_voice and contacts_start_task by specifying the chat channel.

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?

There is no guidance on when to use this tool versus the voice or task start tools, nor any exclusions or alternatives mentioned. The description only states the basic action without contextualizing its appropriate use.

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