タスク一覧

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

The annotation readOnlyHint already declares this a read-only operation, and the description adds a non-obvious behavioral nuance: API-completed tasks appear by default and can be hidden via clear-completed-tasks. This goes beyond the annotation and is highly relevant for correct invocation.

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 three short sentences, front-loaded with the core purpose and immediately followed by the key filtering and completion nuance. Every sentence earns its place, and there is no redundancy or filler.

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?

Despite having 11 parameters, all are fully documented in the schema, and the description covers the essential behavior and a crucial default that would otherwise be easy to miss. As a read-only list operation, it provides adequate context for correct usage without needing to explain return values (no output schema).

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%, so the baseline is 3. The description adds value by summarizing that filtering is possible and by clarifying the default inclusion of completed tasks (related to showCompleted), but it does not elaborate on each parameter beyond what the schema already documents. This meets but does not exceed 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 states a specific action ('list tasks') and the resource ('in a task list'), distinguishing it clearly from get-task (single task) and list-tasklists (listing task lists). It also mentions filtering capability, making the purpose unambiguous and immediately usable.

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?

It explicitly mentions that API-completed tasks are included by default and that clear-completed-tasks can hide them, guiding the agent toward an alternative tool for that specific need. While it doesn't exhaustively say when not to use other siblings, it provides useful context about the filtering and completion behavior.

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