Add assignees

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

No annotations are provided, so the description must carry the full burden. It only restates the HTTP method and endpoint, failing to disclose whether the add is appending or replacing, permissions required, idempotency, or side effects. A POST mutation tool requires more behavioral context.

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 short but includes redundant technical details like the full HTTP path and 'Tags: Task'. While concise, it lacks critical information about functionality and parameters, making it underspecified rather than efficiently structured.

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 presence of sibling tools for assignee management and a nested schema, the description is severely incomplete. It does not explain how this tool relates to 'attach_an_assignee' or 'remove_assignee', lacks return value info (no output schema), and leaves parameter usage ambiguous.

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%, yet the description adds no meaning to the parameters. It does not clarify what 'assignees' expects (user IDs, emails?), nor the format of 'taskId'. The description fails to compensate for the lack of schema documentation.

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 states 'Add assignees' and specifies the HTTP endpoint, making the verb and resource clear. However, it does not distinguish this tool from siblings like 'weeek_attach_an_assignee' or 'weeek_remove_assignee', which may have overlapping functionality.

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. There is no mention of prerequisites, restrictions, or context for when to add assignees vs. attach/detach.

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