publish_skill

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

Minimal disclosure beyond the action. With no annotations, the description should cover side effects (e.g., overwriting canonical, sync behavior) but does not. It implies state change but lacks detail.

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 with no filler. It is efficient but very brief.

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 6 parameters, 0% schema coverage, and no annotations, the description is far from adequate. It does not explain output (despite output schema) or parameter usage, leaving the agent with minimal actionable guidance.

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 0%, yet description adds no information about parameters like 'draft_or_path', 'slug', 'targets', or 'visibility'. The description fails to compensate for missing parameter descriptions.

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 action ('publish') and the resource ('validated draft as canonical') with optional sync. It distinguishes from siblings like 'validate_skill' or 'update_canonical_skill' by focusing on the promotion step.

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 vs alternatives (e.g., 'update_canonical_skill', 'rollback_scope'). It does not mention prerequisites like requiring a validated draft.

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