pdm_tasks_list

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

No annotations provided, so description carries full burden. Discloses configuration requirement and that it lists 'recent' tasks, but does not define 'recent' or mention pagination, ordering, or any side effects. Adequate but lacks detail.

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?

Extremely concise with two short sentences. Front-loaded with purpose and includes a prerequisite. No wasted words.

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?

Simple tool with one optional parameter and an output schema present. Description covers core functionality and a key prerequisite. Lacks definition of 'recent' but is otherwise complete for a diagnostic list operation.

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% for the single parameter 'proximo_target', with a clear description in the schema. Tool description adds no extra meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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?

Description clearly states 'list recent PDM tasks across all remotes', providing specific verb (list), resource (PDM tasks), and scope (across all remotes, recent). Distinguished from sibling tools like pbs_tasks_list and pve_tasks_list by naming and context.

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?

Indicates use case with 'DIAGNOSE (LOW)' for diagnostic purposes and includes a prerequisite ('Needs PROXIMO_PDM_* config'). Does not explicitly state when to avoid this tool in favor of siblings, but naming conventions make it clear that this is for PDM tasks only.

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