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

Annotations cover safety profile (destructiveHint=true, openWorldHint=true, idempotentHint=false). The description adds valuable context: 'draft keeps it hidden; published sends it to assignees'apps' and 'several user ids make one group task' - behavior not captured in annotations. Minor gap: doesn't mention the destructive implications noted in annotations.

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?

Front-loaded with WRITE prefix and action, then key behavioral notes, then API path. Efficient and well-organized, though the API path is somewhat redundant for an agent.

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?

Complete for a creation tool with full schema coverage and annotations. The status behavior and group-task semantics are the critical non-obvious details, and they're covered.

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 schema fully documents all 9 parameters. The description reinforces the status enum semantics and group-task behavior for user_ids, adding some value, but baseline 3 is appropriate given the schema does the heavy lifting.

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+resource ('create one quick task on a task board') and scopes it. Clearly distinguishable from connecteam_list_task_boards, connecteam_list_tasks, and connecteam_list_task_labels siblings.

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?

Explains the draft/published status behavior which implies when to use each, but no explicit when-to-use-this-vs-alternatives guidance. No exclusions or prerequisites stated.

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