teamleader_create_task

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

No annotations are provided, so the description carries full behavioral disclosure burden. It only states 'Create' and required fields, with no mention of side effects, permissions, reversibility, or response format. This is a significant gap for a mutation tool.

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 sentences, front-loaded with purpose, and no filler. Every piece of text adds information: action, required fields, and a helper tool reference. Ideal conciseness.

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?

With 10 parameters and no output schema, the description does enough by identifying required fields and pointing to a helper for a key parameter. The schema already describes each parameter in detail. It falls short only in not describing the return value or potential errors, but for a create tool this is acceptable.

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 100% coverage for parameters, so the baseline is 3. The description adds extra value by calling out the three required properties (title, due_on, work_type_id) and providing a specific lookup workflow for work_type_id, which is not fully explicit in the schema.

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 'Create a new task in Teamleader Focus' with a specific verb and resource. It also lists the three required fields, making the purpose unambiguous. However, it does not explicitly distinguish this from sibling create tools, relying on the name and context.

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 gives concrete usage guidance by stating required fields ('title, a due date and a work type') and directing users to teamleader_work_types_list to obtain a valid work_type_id. It covers prerequisites but does not discuss when not to use or alternatives (e.g., teamleader_list_tasks for reading).

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