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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds behavioral context: pagination, ordering by board position, and that every task includes an app_url deep link to give to the user. It does not describe response shape or rate limits, but for a read-only list tool this is adequate. No contradictions.

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 description is long but dense with useful information. It front-loads the core purpose and then logically groups filters (tickets, plan-my-day, assignments, etc.). Every clause contributes value, though it could be slightly more organized with bullet points. Overall, the length is justified by the tool's complexity.

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?

Given the large number of parameters, lack of output schema, and minimal schema descriptions, the description covers major use cases well: ticket filtering, plan-my-day date ranges, milestone/priority/tag/assignee filters, and the helpful app_url deep link. It does not explain all parameters or response structure, but for a list tool this is strong contextual coverage.

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?

The schema has ~40 parameters with almost no descriptions (0% coverage). The description compensates by explaining key filters (project_id, sprint, sprint__isnull, parent_id, is_completed, depth, search, title__icontains, description__icontains, has_ticket, status, date/time filters). It does not cover every parameter (e.g., progress, importance, story_points, assigned_to_me), but it explains the most important ones and the __gte/__lte/__isnull conventions.

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 clearly states 'List tasks the user can access', providing a specific verb and resource. It immediately distinguishes itself from sibling tools like list_projects and list_sprints by noting 'Rich filtering' and detailing the many filter options, making its purpose 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 description explicitly names alternative tools for mutations ('To assign/change status/tag a ticket use the task tools (task_assign_user, partial_update_tasks, add_tag_tasks)') and provides concrete use cases with filter suggestions, such as "Open tickets" and "Plan-my-day". This tells the agent when to use this tool versus alternatives.

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