Change task parent

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

No annotations are provided, so the description carries full burden. It fails to mention behavioral traits such as whether the task is reordered, what happens to subtasks, or any side effects. The presence of 'after' and 'before' parameters hints at ordering but is not explained.

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 very concise, but includes redundant elements like 'Tags: Task' and the full endpoint. While short, it sacrifices informativeness. Every sentence earns its place but lacks substance.

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 no output schema, no annotations, and complex nested parameters, the description is incomplete. It does not describe the request/response format, the effect of optional parameters, or the outcome. For a mutation tool, this is insufficient.

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 0%, and the description adds no meaning to the parameters. It does not explain the purpose of 'parentId', 'after', or 'before', which are crucial for correct invocation. The agent has to rely solely on the parameter names.

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 'Change task parent', which indicates the verb and resource. It also includes the HTTP method and endpoint, distinguishing it from siblings like weeek_change_board or weeek_complete_task. However, it could be more specific about what changing parent entails.

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 provides no guidance on when to use this tool versus alternatives. Among many sibling tools for task updates, no context is given for when changing the parent is appropriate or what prerequisites exist.

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