weeek_create_task

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

No annotations are provided, so the description must carry the full behavioral burden. It does disclose that a parent id creates a subtask and where to source member and tag ids, but it omits key mutation details such as required permissions, side effects (notifications, audit logs), error behavior, and what the operation returns.

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 a single front-loaded sentence that states the core action immediately, followed by a compact enumeration of optional fields. Every clause earns its place and there is 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 10-parameter create tool with no annotations and no output schema, the description is adequate but incomplete. It covers most optional parameters and the subtask behavior, yet leaves out projectId and description, and provides no guidance on when to use the tool versus siblings or what happens after creation.

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 90%, so the schema already documents nearly all parameters in detail. The description repeats most of that information and adds the source tool for member ids (weeek_list_members), but it omits projectId and description parameters entirely. This slightly exceeds the schema but does not compensate for the small coverage gap.

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 opens with a specific verb and resource: 'Create a task.' That clearly identifies the operation and distinguishes it from siblings like list, update, and complete tasks, even without explicitly naming alternatives. The remainder lists optional placement and assignment details, reinforcing the create purpose.

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 no guidance on when to use this tool versus alternatives (e.g., weeek_update_task, weeek_create_board), nor does it state prerequisites or exclusions. It only enumerates optional parameter uses, which is not usage guidance.

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