list-todo-task-lists-delta

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

Annotations already cover read-only, non-destructive and open-world, so the description's job is to add delta mechanics — it does, explaining that repeated calls with state tokens yield incremental changes. It stops short of noting that a first call without a token returns the full set or how the returned delta/next links should be fed back in.

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?

Front-loaded with the concrete result (changed todoTaskLists) before the delta explanation. The second sentence is long and repeats 'todoTaskList' several times, but every clause still carries information about the sync use case.

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?

There is no output schema, and the description never says what a response looks like — the changed collection plus the next/delta token the caller must persist — which is the key thing an agent needs for this tool. The pagination and full-export risks are covered only by the schema descriptions of skiptoken and fetchAllPages.

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% with per-parameter descriptions for select, skiptoken, fetchAllPages, includeHeaders and excludeResponse, so the schema carries the detail. The description only gestures at 'state tokens', which is loosely aligned with skiptoken but adds no syntax or pagination nuance beyond the schema.

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?

States a specific verb and resource ('Get a set of todoTaskList resources') and narrows it to 'added, deleted, or removed', which is precisely what distinguishes a delta call from the plain list. An agent can tell this apart from list-todo-task-lists without inspecting either 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 description makes the intended scenario explicit: maintaining and synchronizing a local store without re-fetching everything. It never names list-todo-task-lists as the non-delta alternative, nor does it say when a full listing is preferable, so routing is implied rather than stated.

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