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

Annotations already declare the mutation and open-world profile, and the description adds genuinely useful context beyond them: it requires the user's Cotlet API key with app access, it runs without a confirmation prompt, and it produces no client-visible output. Auth and side-effect scope are both disclosed.

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 opening fragment ('Houzz Pro: Task on a project or lead, assigned to...') restates the sentence immediately following it, so the lead is redundant. The internal tension between 'assigned to... client' and 'nothing reaches a client' also costs clarity.

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?

Covers auth, confirmation behavior, and scope, which is reasonable for a no-output-schema tool. However, the contradictory client-assignment language leaves the agent unsure whether a client can be an assignee, and it says nothing about the returned identifier or post-creation state.

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 all five parameters are already documented, giving a baseline of 3. The description adds only marginal meaning (assignee can be team/client/sub, target is project or lead) that largely duplicates 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?

States a specific verb (creates) plus resource (a task), and scopes it precisely: on a lead or project, assigned to a team member/client/sub, surfacing in the Task Center. An agent can readily distinguish it from the sibling houzz-pro_list_tasks.

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?

Provides some context (it runs without asking, and targets team/subs rather than clients), but never states when to prefer this over alternatives like list_tasks, or what prerequisite data (project_id vs lead) selects one path. Usage is implied rather than explicit.

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