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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, and destructive=false. The description adds substantial non-obvious behavior: login requirement, notification on assignment to others, authorization over person/content, server-side relationship verification, a 50-per-Beijing-day rate limit, and the absence of a persistent request dedup key with a warning not to auto-resend.

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 dense but front-loads the login requirement and core direct-assignment behavior before operational constraints. Every clause addresses a real usage concern, though the sentence structure is compact to the point of being terse for a complex mutation.

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 non-idempotent, open-world mutation with no output schema, the description supplies authentication, authorization, rate limits, side effects, verification alternatives, and retry caution. This is complete enough for an agent to invoke and handle the tool correctly.

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 only 20%, so the description must compensate. It clarifies assigneeId (omitted means self; assigning others sends notification) and organizationId (organization label with server-side relationship verification), but title and detail remain semantically undocumented beyond their schema constraints, and dueAt is already described in the schema.

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 a specific verb and resource: directly create/assign a task without attaching it to a goal, evidenced by '不挂目标直接派任务' and the goalId=null receipt. This distinguishes it from the goal-attached sibling create_collaboration_task, so an agent can identify the correct tool without opening schemas.

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?

It explicitly gives prerequisites (login required), default behavior (omitted assigneeId means self), side effects (assigning others notifies them), authorization needs, and a daily cap. It also names alternatives for finding people (list_collaboration_task_assignees) and verifying results (list_collaboration_tasks), plus retry guidance after timeout/unknown outcomes.

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