list_my_tasks_tool

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

With no annotations provided, the description must convey all behavioral traits. It only states 'list tasks' without disclosing ordering, pagination, filtering, or what happens if no tasks exist. The output schema may define the structure, but the description itself is insufficient for full 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 a single, clear sentence with no extraneous information. It is appropriately short for a tool with no parameters, and every word serves a purpose. Maximum score for conciseness.

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 zero parameters and the presence of an output schema, the description is nearly complete. It covers the essential purpose and scope. However, it could be improved by mentioning that results are for the authenticated user (implied by 'my') and noting any default behaviors. This minor gap prevents a perfect score.

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?

There are zero parameters, and schema description coverage is 100%. The description adds value by specifying 'current user's tasks,' clarifying the implicit scope. Baseline for no parameters is 4, and this description meets that 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 the current user's tasks' clearly states the verb (List), the resource (tasks), and the scope (current user's). It distinguishes from siblings like get_task_detail, which retrieves a single task, and get_task_status, which checks specific status. This specificity earns a top score.

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 provides basic context ('current user's tasks') but lacks explicit guidance on when to use this tool versus alternatives. No mention of when not to use it or references to sibling tools like search_calls_extensive. The absence of usage direction keeps this at a mid-level score.

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