Plecs Tasks

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

The readOnlyHint annotation already tells the agent this is a safe read with no side effects, so the description's main added value is the 'newest first' ordering, which is genuinely useful. It says nothing about pagination, result limits, or whether completed/failed tasks are included — gaps that matter for a polling-style tool.

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 short sentence with the resource and ordering front-loaded and no wasted words. It is efficient, though borderline under-specified for a tool competing with two similar siblings.

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?

Because an output schema exists, the description need not explain return values, and the zero-parameter schema is trivial. However, for a task-listing tool in a suite with 'plecs_task' and 'plecs_task_result', the description lacks the routing context an agent needs to pick it confidently.

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?

The tool takes zero parameters, so the baseline of 4 applies. There is no parameter information the description could add, and the empty schema is unambiguous.

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 specific verb and resource ('List background tasks') and adds an ordering guarantee ('newest first'), so the agent knows what it returns. It falls short of 5 because it does not distinguish itself from the close siblings 'plecs_task' and 'plecs_task_result', which an agent must choose between.

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 gives no explicit when-to-use guidance, no prerequisites, and no indication of how this differs from 'plecs_task' (get a task?) or 'plecs_task_result' (fetch a result?). Usage is at best implied by the word 'List'.

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