Publish a package to the npm registry with options for dist-tag, access level, dry-run, and one-time password for two-factor authentication.
Publish a package to the npm registry
| Name | Required | Description | Default |
|---|---|---|---|
| otp | No | One-time password for 2FA | |
| tag | No | Dist-tag (default: latest) | |
| path | Yes | Absolute path to the package directory | |
| access | No | Access level for scoped packages | |
| dryRun | No | Run publish without actually publishing |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description fails to disclose behavioral traits like destructive action, authentication needs, or registry modifications. The single sentence offers no behavioral context beyond the verb 'publish'.
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 very concise (6 words) but lacks important context. It is not verbose but would benefit from more detail to be fully useful.
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 5 parameters, no output schema, and no annotations, the description is incomplete. It does not cover workflow, error states, or success conditions, leaving significant gaps for an AI agent.
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 descriptions. The tool description adds no additional meaning beyond what the schema already provides, so it meets the baseline but does not enhance understanding.
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 'Publish a package to the npm registry' with a specific verb and resource. However, it does not differentiate from sibling tools like 'unpublish' or 'pack', which have related but distinct purposes.
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 provides no guidance on when to use this tool versus alternatives, nor does it mention necessary prerequisites such as authentication or package.json requirements.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.