forge_skills

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly indicates a read-only listing behavior, explains the conditional filtering, and names the data source (SKILL_MAP). It does not discuss error cases or return structure, but for a simple list operation the disclosed behavior is sufficient.

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?

Two sentences with zero wasted words. The main purpose is front-loaded, and the conditional variations are presented in a logical order that an agent can parse quickly.

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 tool is simple: one optional parameter, no required inputs, and no output schema. The description covers the purpose, the valid parameter values, and the behavioral difference between the two call forms. It leaves minor ambiguity about the exact return shape, but nothing essential for invoking the tool correctly is missing.

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 schema already documents the phase parameter at 100% coverage, establishing a baseline of 3. The description adds meaningful value beyond the schema by enumerating the valid phase keys and explaining how the parameter changes the result set.

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 verb and resource: 'Lists available skills.' It further clarifies two modes of operation (with or without a phase key), making the purpose unambiguous. It does not explicitly differentiate itself from sibling tools like forge_skill, though the behavior is specific enough to infer the distinction.

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 gives clear guidance on when to use each mode: provide a phase key to get phase-specific skills, omit it to list everything. It does not mention alternatives or when not to use the tool, but the conditional usage context is explicit and actionable.

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