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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false). The description goes well beyond by disclosing the login requirement, the OWNER/ADMIN role gate, the failure mode organization_forbidden and its cause, and where the assignee sees the task — none of which structured fields provide.

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 bracketed blocks (auth, chain, pitfalls) are front-loaded and each sentence carries operational value. Slightly dense with some repetition of the timezone format, but 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?

With no output schema, the description still tells the agent who can call it, what the assignee will see, and how to continue the workflow. It omits only the concrete response shape and whether duplicate pending tasks are rejected (idempotentHint=false is asserted but not explained).

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 100%, so the baseline is 3, but the description adds a genuine disambiguation: assigneeId is a userId, NOT a membershipId, which the schema does not state. It also restates the timezone-aware ISO requirement for dueAt, which the schema already covers.

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 (新建一条任务 in 组织) plus the assignment target (指派给一位在册成员), and the scoping to the organization space distinguishes it from the sibling create_collaboration_task/create_task_series. An agent can select it without opening the schema.

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 【组合链】 section names the prerequisite tool (list_organization_members), the exact field to carry over (user.id), a user-confirmation step, and the follow-up tools for progress and status (list_my_organization_tasks / set_organization_task_status). Explicit when-to-use and routing to siblings.

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