create_task

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

With no annotations, the description carries the behavioral burden. It clearly states the creation action and identifies two meaningful field constraints (Unix timestamp for complete_till, enumerated task types). It does not mention what the response contains, permission requirements, or side effects beyond creation.

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?

Two tight sentences, no filler. The core action and the two most important field semantics are front-loaded, and every clause adds information needed to invoke the tool correctly.

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 creation tool with 6 parameters and no output schema, the description covers the essential semantics but leaves out return behavior and any guidance on optional fields (task_type_id, responsible_user_id) or prerequisites. The schema fills parameter details, so this is adequate but not complete.

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 100%, so the baseline is 3. The description adds a little context by calling out complete_till as a Unix timestamp and mapping task type IDs to labels, but these details already appear in the schema, so it does not materially exceed baseline.

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 names a specific verb and resource ('Create a task') and specifies the linkage targets (lead, contact, or company), which clearly separates it from sibling tools like create_lead, create_company, list_tasks, and complete_task.

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?

Usage is implied by the verb and resource: call this when you need to create a task. However, it does not explicitly say when to prefer this over add_note or complete_task, nor does it state any exclusions or prerequisites such as the linked entity needing to exist.

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