skill_files

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

No annotations are provided, so the description carries the full burden. It implies a read operation by stating 'List...', but does not explicitly confirm it is read-only or describe side effects, permissions, or rate limits. The exclusion of SKILL.md is noted, but overall transparency is adequate but not thorough.

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 sentences, each earning its place: first sentence defines the action, second provides usage guidance. It is front-loaded and contains no unnecessary words. Ideal conciseness.

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 low complexity (1 required parameter), high schema coverage, and presence of an output schema, the description covers the essential aspects: what it does, usage recommendation, and key exclusion (SKILL.md). It could be more complete by specifying the return format, but the output schema likely covers that, making the description sufficient.

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 100% (the single parameter 'name' is described with an example). The description does not add any meaning beyond the schema, so it meets the baseline of 3. It does not compensate with additional parameter context.

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 supporting files in a skill directory (excludes SKILL.md)', providing a specific verb and resource. It distinguishes itself from siblings like skill_file_get (which gets a single file) by implying a listing operation. The examples of resources (examples, references, templates) further clarify the scope.

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 says 'Use this to discover additional resources... beyond its main SKILL.md content', which gives a clear use case. However, it does not explicitly state when not to use it or mention alternatives like skill_file_get for retrieving specific files. Some guidance is present but lacks exclusions.

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