task_device_tasks__list_tasks

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds nothing beyond restating the endpoint: it does not mention pagination defaults (50, max 1000), the local-only 'fields' projection, or anything about result volume or ordering.

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?

It is short and front-loaded, but three segments say the same thing twice ('List tasks' then 'List all device tasks'), and the parenthetical endpoint adds little for an agent that already has the tool name.

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 paginated list endpoint with no output schema, the description should at minimum explain what a device task is and how paging/empty results behave. It leaves both unaddressed and gives no routing guidance among the three sibling task tools.

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%, so pageSize, pageToken, and fields are fully documented in the schema and the baseline applies. The description adds no parameter meaning and its 'matching criteria' wording could mislead an agent into expecting filter parameters that do not exist (additionalProperties is false).

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 verb and resource ('List tasks', endpoint GET /v1/device_tasks), so the basic purpose is clear. But it then repeats itself ('List all device tasks matching criteria') without saying what a device task is or how this differs from sibling task_device_tasks__get_task or task_device_tasks__list_task_runs.

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?

There is no guidance on when to call this versus task_device_tasks__get_task (single task) or task_device_tasks__list_task_runs (runs of a task). The phrase 'matching criteria' implies filtering, but no filtering parameters exist, leaving the agent to infer the selection semantics.

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