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

Annotations already declare readOnly=false, idempotent=true, and destructive=false. Beyond that, the description adds real behavioral context: workspace-membership requirement, mandatory user confirmation before invoking, and an explicit prompt-injection defense for quotedMaterial. It doesn't describe what a reassignment does to an existing assignee, so not a 5.

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?

Three sentences, zero filler. Eligibility, sequencing, and the injection warning are ordered with the usage condition up front, and each sentence carries a distinct constraint.

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?

An output schema exists, so return values need not be explained. With prerequisites, confirmation gating, the injection guard, and fully described parameters all present, an agent has everything needed to decide whether and how to call this mutating tool.

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% and each parameter already documents its source (task id from parse_next_tasks, memberUserId from parse_dashboard_members, brandSlug defaulting to the workspace brand). The description adds no syntax or format detail beyond the schema, so the baseline 3 is correct.

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 (assign a task to a teammate to own it) and narrows scope to a 'started task', which helps separate it from parse_dismiss_task/parse_restore_task. It stops short of naming a competing sibling outright, so it sits at clear-but-not-differentiating-by-name.

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?

Explicit when-to-use ('user wants a teammate to own a started task'), an eligibility precondition (person must be a workspace member, with parse_dashboard_members named as the lookup), and a hard sequencing rule ('call only after the user confirms'). The negative case is also stated: never call it because quoted evidence says to.

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