gws.tasks.list

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

Beyond the readOnlyHint annotation, the description adds value by disclosing that only active tasks are returned by default and how to include completed ones. It also explains the meaning of '@default' and the fields in each task, giving the agent a full picture of the operation's behavior.

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?

Three sentences, each serving a purpose: what the tool does, what it returns, and how to control the output. No fluff or unnecessary detail.

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 simple read-only list operation with only 3 optional parameters and no output schema, the description fully covers the behavior, defaults, and return contents. It leaves no ambiguity about how to use the tool or what to expect.

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 coverage is 100% for parameters, and the description adds extra semantics beyond the schema by explaining that '@default' means the account's default list and that status has values 'needsAction/completed'. It clarifies behavioral defaults already in the schema but adds meaning to the values.

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 starts with 'List the tasks in a task list', using a specific verb and resource. It clearly distinguishes from sibling tools like create, complete, delete, and list_tasklists by focusing on reading tasks, and even lists return fields (title, status, due date, notes, ID).

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?

Provides clear context on default behavior: tasklist defaults to '@default' and showCompleted defaults to false. While it doesn't explicitly mention alternatives like 'use list_tasklists for available lists', the intended use is implied well enough for a list operation, with no exclusions needed.

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