clawhub_list_skills

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

No annotations are provided, and the description does not disclose behavioral traits such as whether it is read-only, rate limits, side effects, or auth requirements. It only describes the core function, leaving the agent without important safety or behavior context.

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 all key information front-loaded: the action, resource, and pagination method. It lists optional parameters concisely without extraneous words, earning its space.

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?

The description lacks details about the response format (e.g., list of skills, presence of nextCursor) and does not mention error handling or rate limits. Given the absence of an output schema and annotations, the description alone is not fully complete for an agent to confidently invoke the tool, though it covers the basics.

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?

With 0% schema description coverage, the description adds meaning to all three parameters: notes that cursor comes from previous response.nextCursor and that nonSuspiciousOnly is a boolean filter. This compensates for the lack of schema descriptions, though it could be more detailed (e.g., default values).

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 'List skills in the catalog with cursor pagination', specifying the verb 'list' and the resource 'skills'. This distinguishes it from sibling tools like clawhub_search (search) and clawhub_get_skill (single item).

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 guidance on usage by mentioning optional parameters (limit, cursor, nonSuspiciousOnly) and how to obtain cursor from previous response.nextCursor. However, it does not explicitly state when to use this tool over alternatives like clawhub_search, though the distinction is implied.

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