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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description contributes nothing further: no mention of pagination via cursor, result ordering, or the fact that both roles are merged when the role filter is omitted. The phrase 'posted or was awarded' faintly maps to requester/provider but is not explanatory.

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 a single front-loaded phrase with zero waste, which is structurally clean. However, the extreme brevity reflects under-specification rather than disciplined conciseness, so it does not earn a high score.

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 four-parameter, cursor-paginated, read-only query tool with no output schema, the description should at least hint at the return shape or pagination behavior. It provides none of that, leaving the agent to rely entirely on structured fields for a tool whose result set semantics (personal tasks across two roles) are the core value.

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 every parameter (role, limit, cursor, status) is already documented in the schema, including the cursor 400 error and limit clamping. The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

Tautological: description restates name/title.

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 use this tool versus the many adjacent list tools (list_tasks, my_bids, my_disputes, my_providers, task_feed). The agent must infer that this is the personal cross-role task list, with no stated conditions, exclusions, or alternatives.

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