vibekit_list_tasks

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

No annotations are provided, so the description carries the full burden on behavioral disclosure. It only says 'List recent tasks' without mentioning read-only nature, pagination, ordering, or whether it returns full task details or summaries. This is insufficient for the agent to predict behavior.

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?

The description is a single sentence with no redundant wording, making it highly concise. It is front-loaded and easy to parse, though perhaps too sparse to convey full functionality.

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?

With no output schema and no annotations, the description is incomplete. It does not explain what fields are returned, how 'recent' is defined, or whether all tasks are included. This leaves the agent with ambiguities about the tool's behavior and output.

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 input schema already provides rich descriptions for both parameters, including the enum values and a note about 'complete' vs 'completed'. The description adds no additional parameter context, so the baseline of 3 for full schema coverage 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?

The description clearly states the tool lists tasks, using the specific verb 'list' and the resource 'tasks', and adds 'recent' to indicate scope. This distinguishes it from sibling tools like vibekit_get_task (single task) and vibekit_submit_task (create task).

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 provides no guidance on when to use this tool versus alternatives such as vibekit_get_task or vibekit_wait_for_task. It does not mention any exclusions or preferred contexts, leaving the agent without clear selection criteria.

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