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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real value by disclosing the shape of what comes back (field list, status vocabulary draft/published/completed, Unix-seconds timestamps). Pagination semantics live in the schema rather than the description, so it stops short of 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?

Two sentences, front-loaded with the action and resource, followed by returned fields, then filters and the endpoint. The field enumeration is dense but earns its place since there is no output schema; nothing is redundant.

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, describing the returned fields is genuinely necessary and done well, and all 7 parameters are covered by the schema. Missing are guidance on pagination behavior in the description text and any cross-reference to how task_board_id is obtained.

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 every parameter is already documented with bounds, defaults and enum values. The description restates the filter axes but adds no syntax or format detail beyond the schema, which is the baseline-3 case.

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 ('List tasks on a task board'), then enumerates the returned fields (title, assignee ids, status, times, labels, sub-tasks) and the supported filters. This clearly separates it from siblings like connecteam_list_task_boards and connecteam_list_task_labels.

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 names the filter dimensions (status, users, labels, task ids) and gives the underlying endpoint, which implies retrieval usage, but it never states when to reach for this tool versus e.g. connecteam_list_task_labels or a single-task lookup. No prerequisites or exclusions are given.

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