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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false). The description adds real behavioral context beyond them: that due_before returns only open tasks 'soonest first' (a sort behavior not in the schema) and that it requires the user's Cotlet API key with access to the app (auth requirement).

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-loads the resource and scope before routing guidance. Slightly redundant, since 'Tasks across jobs, with the job, assignee and due date' and 'Lists the tasks that make up jobs' restate the same idea, but overall it is tight and readable.

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, filter-only list tool with annotations carrying the safety profile and a cursor parameter handling pagination, the description covers purpose, filters, ordering and auth. No output schema exists, yet listing the returned fields (job, assignee, due date) is adequate disclosure.

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 all four parameters, establishing the baseline of 3. The description's added meaning ('due_before returns open tasks ... soonest first') contributes only a minor sort-order detail beyond what the schema states.

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 clear verb+resource ('Lists the tasks that make up jobs') and names the key fields returned (job, assignee, due date). It distinguishes tasks from jobs conceptually, but never names the obvious sibling taxdome_list_jobs, so it stops short of explicit sibling differentiation.

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?

Gives clear context for invoking it: 'Use it to find what a team member still owes,' supported by the filter options (job, assignee, due_before). There are no explicit when-not conditions or named alternatives, but the intended use case is unambiguous.

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