Get a task list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond those hints: the returned resource is metadata-only, '@default' can resolve the real id, and actual tasks are not included.

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 carrying distinct information: what is fetched, the '@default' special value, and the key limitation that tasks are elsewhere. The most important identifying information is front-loaded.

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 one-parameter, read-only, idempotent fetch with no output schema, this description is complete. It states the resource identity, the parameter's special value, the returned fields, and the boundary between task lists and tasks. Nothing an agent needs to call it correctly is missing.

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% and the parameter description already documents tasklist_id, including the '@default' behavior. The description reinforces this and adds the purpose 'useful to resolve its real id', but it does not substantially extend the schema's meaning. Baseline 3 is appropriate.

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 uses a specific verb ('Fetches'), names the exact resource ('one task list by id'), and lists the returned fields. It clearly distinguishes itself from list_tasklists (list all) and list_tasks (fetch tasks) by scoping what this tool does not return.

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 gives clear context for when this tool is appropriate: fetching a single task list, including via '@default'. It also explicitly directs task retrieval to list_tasks, and the singular-by-id wording implicitly distinguishes it from list_tasklists. It does not explicitly exclude list_tasklists, but the distinction is clear enough.

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