Create Task

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about required permissions, side effects on the parent list/project, whether the call is idempotent, or what the response contains. The only added context is the structural note that task_list_id belongs to a project.

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 the action and required inputs, followed immediately by the discovery path. No filler.

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 seven-parameter mutation tool with no annotations and no output schema, the description covers required inputs and ID discovery but omits creation semantics and return behavior, which an agent must otherwise guess.

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 coverage is 100%, so the schema already documents all seven parameters and even repeats the ID-discovery hints. The description adds one piece of meaning beyond it: that task_list_id belongs to a project, clarifying the hierarchy an agent must respect.

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?

States a specific verb and resource ('Create a new task in Productive.io') and the required inputs, which distinguishes it clearly from siblings like productive_get_task, productive_update_task, and productive_list_tasks.

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?

Gives an explicit prerequisite (title and task_list_id) and routes the agent to productive_list_tasks with a project_id to discover valid task_list IDs. It doesn't contrast against productive_update_task or explain when creating is inappropriate, so it stops short of the top band.

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