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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds a genuine behavioral detail, the requirement for the user's Cotlet API key with app access, but says nothing about pagination, result caps, or how many tasks are returned for all jobs, which is the main behavioral risk for an unfiltered list.

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?

It is front-loaded and short, but the field list 'assignees, deadline, checklist and status' is stated twice in the first two sentences, which is redundant waste. Trimming the repetition would make it tighter.

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?

For a read-only list tool with full schema coverage and annotations, the description covers scope, defaults, filtering, and the auth prerequisite, so an agent has enough to call it correctly. The absence of any note on result volume or paging is the only real gap.

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 coverage is 100% and all three parameters carry their own descriptions, so the schema does the heavy lifting. The description restates the same semantics (status default, assigned_to_me scope) rather than adding format or syntax detail, so the baseline 3 applies.

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 specific verb (list) and resource (tasks) and enumerates the fields returned (assignees, deadline, checklist, status), so an agent can distinguish it from buildertrend_create_task and the various list_jobs/list_change_orders siblings. It stops short of naming an alternative tool explicitly, so it is clear but not sibling-routing.

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?

It gives usage context for the parameters ('one job or for all jobs', 'Status defaults to open', 'Set assigned_to_me to see only your own'), which implies how to scope the call. However, there is no explicit when-to-use guidance against alternatives such as buildertrend_get_schedule or the change-order/daily-log listers.

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