Get 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 the device-scope constraint and the task types returned, but says nothing about pagination, result volume, or whether admin-assigned tasks require elevated privileges.

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 front-loaded sentence with the scope qualifier at the end and no filler. It is efficient, though its brevity is partly under-specification rather than pure economy.

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 tool with three undocumented, untyped parameters and no output schema, the description should explain the expected request payload or at least the response shape. As written, an agent can tell what the tool conceptually does but not how to actually invoke it with meaningful input.

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 0% across three parameters (form, params, json_body) that are generic, opaque wrappers. The description does not explain what any of them carry or how they map to filtering tasks, leaving the caller to guess the payload shape entirely.

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 (List) and resource (pending security tasks) and clarifies the two task categories in parentheses (at-risk password / admin-assigned). The device scoping further narrows it, so an agent can distinguish it from adjacent read tools like get_auth_requests_pending without opening a 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 'for the current device' implies a context constraint, which is useful, but the description never says when to prefer this over alternatives or what prerequisites (authenticated session, device identity) are required. Usage is only implied, not directed.

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