list_my_tasks

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action 'List' but does not mention pagination, ordering, or the limiting effect of maxResults, despite the description saying 'all'. The mismatch between 'all' and the maxResults parameter is a transparency concern, as the tool will not always return all tasks.

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 a single, front-loaded sentence with no unnecessary words. It immediately states the action and scope, earning a perfect score for efficiency.

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 is adequate for a simple list operation, but it lacks important context such as the meaning of 'unresolved' and the interaction with maxResults. Without an output schema, some information about return values would be helpful, though not strictly required.

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 provides 100% coverage for the single parameter (maxResults) with a clear description. The tool description adds no additional meaning to the parameter, and the word 'all' even conflicts with the parameter's purpose, so this dimension stays at the baseline.

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 'List all unresolved tasks assigned to current user' clearly specifies the action (list), the resource (tasks), and the scope (unresolved, assigned to current user). This distinguishes it from siblings like list_my_board_tasks, which focuses on board tasks, and list_subtasks, which targets subtasks.

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 implies usage for retrieving the current user's unresolved tasks, but it does not explicitly state when to use this tool over alternatives or provide any exclusions. With many sibling list tools, the lack of explicit differentiation is a gap, but the scope is clear enough to infer typical use.

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