list_my_tasks

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

No annotations are provided, so the description must carry the burden for behavioral traits. It does not disclose any behavioral aspects such as read-only nature, data scope (e.g., current user only), pagination, or error conditions. Lacks transparency.

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 relatively concise with a clear structure (purpose sentence followed by Args block). It is not overly verbose, but could be more front-loaded by omitting the 'Args:' label if not needed.

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?

The description covers the basic operation and one parameter well, but lacks context about important aspects like pagination, size limits, or whether the list is exhaustive. With an output schema (unseen), return values are not necessary to describe, but more guidance on filtering beyond status would improve completeness.

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 description adds significant meaning to the 'status_filter' parameter beyond the schema, specifying allowed values ('open', 'closed', 'in_progress') and default. Schema description coverage is 0%, so the description compensates well.

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 the tool lists tasks assigned to the user. It uses specific verb 'lấy danh sách' (get list) and resource 'task', and distinguishes from sibling tools like 'get_issue_details' (single issue) or 'get_today_logs' (time logs).

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 offers no guidance on when to use this tool versus alternatives. No explicit when-to-use or when-not-to-use information is provided, leaving the agent without context for selection among sibling tools.

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