List skills

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

No annotations provided, so description must cover behavioral traits. It doesn't mention whether the operation is read-only, has side effects, requires authentication, or returns paginated results. 'List available skills' implies safe reading but is insufficient.

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?

One sentence, no wasted words. Clearly communicates the core function. Could be more informative without losing conciseness, but it is appropriately front-loaded.

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 3 optional parameters, no annotations, no output schema, and nearby siblings, the description is incomplete. It does not explain what 'available' means, the output format, or how filters interact. Leaves agent to guess.

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 description coverage is 0%, so description must compensate. It lists parameters (folder, search, source) but provides no details on their format, default behavior, or how they combine. The phrase 'optionally filtered' adds minimal value.

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 it lists available skills with optional filtering, using specific verbs and resource. It distinguishes from siblings like skills__configure, skills__get, skills__invoke, skills__reload by focusing on listing rather than configuring, retrieving a single skill, invoking, or reloading.

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 (e.g., when to use skills__get instead). Lacks context about prerequisites or scenarios where filtering would be appropriate.

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