pdm_tasks_list

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

Labels the tool as READ-ONLY and states no state change. Returns a list of task dicts. Lacks details on pagination or limits, but output schema exists to fill gaps.

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?

Three sentences, front-loaded with READ-ONLY and purpose. Efficient, though could be slightly tighter.

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?

Given no annotations and presence of output schema, the description covers read-only nature, sibling alternative, and config prerequisite. Complete for a list tool.

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?

Single optional parameter with 100% schema coverage. Description adds no extra meaning beyond schema, as expected for high coverage.

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 clearly states the tool lists recent PDM tasks across all remotes, specifying task states. It distinguishes from sibling pve_tasks_list by noting the alternative for direct remote task lists.

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?

Explicitly states the tool is read-only and no state change. Provides a direct alternative (pve_tasks_list) and mentions prerequisite config (PROXIMO_PDM_*).

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