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 discloses that the result includes 'org' and 'bound' (some output context), and notes multi-project membership, but it does not reveal permissions, idempotency, side effects, or error behavior. For a mutation tool, this is a significant transparency gap.

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—two sentences with no fluff. The main action is front-loaded. The second sentence about the result is cryptic but not verbose. It earns a high score for efficiency, though the cryptic result note could be clearer.

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?

With an output schema present, return values need not be explained. However, the tool has four parameters (two optional) and no annotations; the description does not explain when to use section_id or agent override, nor does it address idempotency or failure modes. For a mutation tool in a rich context, this is incomplete.

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?

All four parameters have schema descriptions (coverage 100%), so the schema already documents them. The tool description adds no extra meaning about parameters like agent override or section_id. The baseline 3 is appropriate because the schema covers the semantics.

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 clear verb and resource: 'Add a task to a project.' It also adds the key semantic that tasks can belong to multiple projects, which differentiates it from the sibling work_remove_from_project. The purpose is unambiguous and specific.

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 implies usage (add a task to a project) and the multi-project note hints at when it's applicable, but it does not explicitly contrast with the sibling work_remove_from_project or state when not to use it. The guidance is implied rather than explicit, so it falls short of a clear when/when-not statement.

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