contacts_start_task

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 only states the creation action and does not disclose any side effects, required permissions, rate limits, or what happens upon creation. 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 concise sentence with no fluff or redundancy. It is front-loaded with the action. However, given the tool's complexity (5 parameters), the brevity borders on under-specification, but not to the degree of a tautology.

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 tool has 5 parameters, no schema descriptions, no annotations, and an output schema, yet the description is merely 'Create a task contact.' This is grossly insufficient for an agent to understand how to invoke the tool correctly, what inputs are needed, or what to expect in the output.

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 input schema has 5 parameters with 0% schema description coverage, and the tool description adds no parameter information. It does not explain the meaning or purpose of instance_id, contact_flow_id, name, attributes, or description. The description fails to compensate for the missing schema descriptions.

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 'Create a task contact.' clearly states the action (create) and the resource (task contact). This distinguishes it from sibling tools like contacts_start_chat and contacts_start_outbound_voice by the specific contact type. However, it does not elaborate on what a task contact is, which limits full clarity.

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?

No guidance is provided for when to use this tool versus alternatives. There is no mention of prerequisites, scenarios, or comparison with sibling tools like contacts_start_chat. The description simply states the action without any usage context.

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