list-skills

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

Description adds the behavioral context that it searches the .agents/skills/ directory, beyond what annotations (readOnlyHint, idempotentHint) already provide. No contradictions; it's a simple read operation.

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?

Single sentence, front-loaded with action and resource, no filler. Every word earns its place.

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?

For a simple, read-only tool with one optional parameter and an output schema (implied), the description is complete. It sufficiently covers what the tool does and its context.

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 coverage is 100% with parameter 'workingDir' already described in the schema. The description does not add new semantic meaning beyond what the schema provides. Baseline 3 applies.

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?

Description clearly states 'Discover available Codex skills from .agents/skills/ directory' with a specific verb and resource. It distinguishes itself from siblings like ping, help, brainstorm, etc., which do not relate to skills discovery.

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 for discovering skills but does not provide explicit guidance on when to use this tool versus alternatives (e.g., other tools like brainstorm or fetch-chunk). No exclusions or context about when not to use it.

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