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

Annotations already cover readOnly/openWorld/non-destructive, so the bar is lower. The description still adds real value: the sort order (by due date), the exact field set returned (assignee, due date, status, owning lead/project), the possible assignee types, and the API-key access requirement — context not present in the 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?

The scoping info is front-loaded, but 'sorted by due date' and the returned-field list are stated twice ('sorted by due date, with assignee and status' vs the near-identical second sentence), and the 'Houzz Pro:' prefix is redundant with the title. Size is acceptable but the repetition is wasteful.

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 carries the burden of describing returns, and it does so (task fields and owning lead/project), plus the auth prerequisite. It omits pagination/result-limit behavior, which is the only notable gap for a simple 3-parameter list 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 description coverage is 100%, so the schema already documents status (with enum and default), assignee, and project_id. The description's note that assignees can be 'team members, clients or subs' essentially repeats the schema text, adding little semantic detail beyond it. Baseline 3.

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 clear verb (list/returns tasks), the resource (tasks from the Task Center), and the scope (sorted by due date, with assignee/status). It is easily distinguished from houzz-pro_create_task. It stops short of naming sibling list tools, but the purpose is unambiguous.

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 'list' framing implies this is the retrieval tool, and the auth prerequisite ('Needs the user's Cotlet API key with access to this app') is stated. However, there is no explicit when-to-use/when-not guidance or mention of an alternative sibling, so usage must be inferred.

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