tasks_tasklists_get

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that retrieval is by ID but does not disclose return shape, potential errors, or external-world caveats. It is consistent with the annotations and minimally transparent, but it contributes little beyond them.

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?

A single, direct sentence with no filler. The verb, resource, and lookup key are all front-loaded, making it immediately scannable and easy for an agent to parse.

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 getter with safety annotations, this is nearly complete: the agent only needs the task list ID, and the schema supplies the default-list special value. The only minor gap is the lack of any hint about the return object shape, which is not critical at this complexity.

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 description coverage is 100%, and the schema already documents the tasklist parameter including the '@default' convention. The description merely echoes 'by ID' and adds no parameter-level meaning beyond what the schema provides.

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 and resource, 'Get a task list by ID,' which clearly identifies a single-resource retrieval operation. It is distinct from siblings like tasks_tasklists_list, tasks_tasklists_insert, and tasks_tasklists_delete without needing to open the schema.

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 phrase 'by ID' implies the intended use case—retrieve one known task list rather than listing all—but it does not explicitly name alternatives or exclusions. An agent must infer when to choose this over tasks_tasklists_list; the guidance is only implicit.

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