yade_list_tasks

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

With no annotations, the description must disclose behavioral traits. It only mentions pagination but does not state that the operation is read-only, that tasks are ordered by recency (implied by skip_newest), or that it returns a subset. More behavioral detail would help an agent choose correctly.

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 single sentence that conveys the core function. Every word earns its place, though it could benefit from slightly more structure (e.g., separating purpose and behavior).

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 the simple list functionality and presence of an output schema, the description is minimally adequate. However, it does not explain the ordering (newest first) or clarify that skipping adjusts the start of the list. An agent could invoke correctly but with some ambiguity.

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 coverage is 100%, so baseline is 3. The description does not add meaning beyond the schema; 'with pagination' aligns with parameters but does not explain their interaction or how skip_newest affects results. No additional value added.

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 verb 'list', resource 'tracked YADE tasks', and includes 'with pagination' to indicate the tool returns a paginated list. While it distinguishes from sibling tools like yade_check_task_status, it could be more explicit about the ordering or intent.

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?

No guidance on when to use this tool versus alternatives such as yade_check_task_status or yade_execute_task. The description lacks any context about prerequisites or preferring this tool for listing all tasks.

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