create_skill

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

With no annotations, the description carries the transparency burden. It discloses error behavior for missing record references (codes 21/22, 43, 44), which is useful, but it does not mention that the tool writes to disk, requires a loaded project, or what side effects creation entails.

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 with no filler. The first sentence defines the action; the second provides a compact, highly specific error mapping. Every part 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?

Given 12 parameters and no output schema, the description is modest. It adds error-handling context but does not explain return values (e.g., new skill ID), prerequisites, or typical usage flows. The rich schema compensates for parameter detail, but broader context 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 input schema has 100% description coverage for all 12 parameters. The description adds no additional meaning to the parameters; it only refers to effects indirectly via the error message. Schema descriptions already handle parameter semantics.

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 states 'Create a new skill with custom properties' with a specific verb and resource. The phrase 'custom properties' distinguishes this generic creator from specialized siblings like create_healing_skill and create_damage_skill.

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 this is the general-purpose skill creation tool, but it does not explicitly name alternatives or state when to use this over specialized creators. No exclusions or comparative guidance is provided.

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