lokalise_create_task

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

No annotations are provided, so the description carries the full burden. It mentions the return value but does not disclose authorization requirements, rate limits, or potential side effects like whether it overwrites existing tasks. The description is adequate but could be more explicit about behavior.

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 concise (two paragraphs and a tip), front-loaded with purpose and required parameters. Every sentence adds value, with no 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 the 16 parameters (100% schema coverage) and no output schema, the description covers essentials: required params, return value, and a usage tip. It is fairly complete for a create operation, though it could mention the returned task structure in more detail.

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 lists required and optional parameters but adds only one minor tip about assignees. It does not provide additional meaning beyond what is 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 it initiates a new batch of translation or review work, listing required and optional parameters and what it returns. It distinguishes itself from sibling tools like lokalise_create_keys or lokalise_create_project by focusing on task creation.

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 clear use cases: assign work to translators, set deadlines, organize sprints. It includes a tip for using assignees for simple setups. However, it does not explicitly state when not to use this tool or mention alternatives, though no direct alternative exists among siblings.

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