publish_skill

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

With no annotations, the description carries full behavioral burden, but it only states the action and scope. It does not disclose whether an existing skill is overwritten, what permissions are required, or any side effects of publishing (e.g., making a global skill visible to all).

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?

A single sentence that is front-loaded with the verb and key information, containing no filler or redundant phrases.

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 description is minimal for a tool with a required nested object and no annotations. It omits critical context such as whether publishing is additive or overwrites, how visibility interacts with agent_key, and what the output schema (response) represents, making it incomplete for reliable invocation.

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 a nested skill object and 3 parameters, but the description provides no parameter-level guidance beyond hinting at 'global or personal' (visibility). With 0% schema_description_coverage, this leaves the agent to guess the meaning of agent_key, meta, tags, triggers, and the required body/description fields.

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 uses a specific verb ('publish') and resource ('skill') with a location ('vault') and scope ('global or personal'), clearly distinguishing this from sibling operations like update_skill, delete_skill, and search_skills.

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?

It states the action (publish new skill) and the scope options (global/personal), implying this is the tool for creating a new skill rather than updating or deleting. However, it does not explicitly name alternatives or state 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.