vibekit_list_skills

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

The description adds context about what skills are ('code patterns and best practices'), which helps set expectations. However, with no annotations, it doesn't explicitly state that this is a safe read-only operation or describe the response format, leaving room for ambiguity.

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 two short sentences, front-loaded with the core action. Every word earns its place, providing both clarity and context without unnecessary detail.

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 scope (1 optional param, no annotations, no output schema), the description is mostly complete. It conveys the essential purpose and what skills are, though it doesn't explicitly describe the return value (e.g., a list of skill names), which is typically implied by 'List'.

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 fully documents the single 'tag' parameter with an explanation and examples, so the description doesn't need to add parameter details. The description adds no extra parameter semantics beyond the schema.

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's function: 'List available implementation skills.' It uses a specific verb and resource, which distinguishes it from sibling tools like vibekit_get_skill that likely retrieve a single skill.

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 implies usage by naming the action 'List', but it provides no explicit guidance on when to use this tool versus alternatives like vibekit_get_skill. No exclusions or alternative references are given.

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