prepublishonly

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

No annotations are provided, so the description carries full burden. It only states it runs the script, but does not disclose potential side effects, permission requirements, or error behavior. For a script runner, more detail on process and outcomes is needed.

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 a single sentence that directly states the action. It is appropriately sized and front-loaded with the key information. No unnecessary text.

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 very minimal. It does not explain the npm lifecycle context (prepublishOnly runs before publish) or how it differs from a plain build. With no output schema and sibling tools, it should provide more context for agent decision-making.

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 description coverage is 50% (args has description, _ does not). The tool description does not add any parameter-specific meaning beyond what is already in the schema for 'args'. No additional clarity on parameters is provided.

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 tool runs the npm script 'prepublishOnly' which executes 'npm run build'. It identifies the specific script, but lacks distinction from the sibling 'build' tool, which might run build directly. Still, it is specific enough for basic understanding.

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?

There is no guidance on when to use this tool versus alternatives like 'build' or 'test'. It does not mention that it is typically executed before publishing or that it is part of the npm lifecycle. The description only states what it does, not when to use it.

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