Set up trusted publishing

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

Annotations only give openWorldHint/destructiveHint, and the description goes well beyond them: it discloses interactive steps, a 2FA approval requirement, that it opens a browser, that some registries only return values for the user to paste, and that the user must click Save. It does not state whether the npm command mutates config remotely or what happens on failure, so not a full 5.

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?

Four dense sentences, front-loaded with the core purpose before the registry-specific branches. No filler, though listing three registry behaviors in one block is slightly compressed.

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?

With no output schema, the description usefully explains what comes back (a settings page fallback, or exact values to fill in) and covers all registry branches. An agent has enough to call it and set expectations for the interactive hand-off.

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 50%: dir and repo are documented, but openBrowser and workflowFile have no descriptions. The description indirectly conveys both (it 'opens the settings page' and targets the 'GitHub release workflow'), yet it never names or maps to those parameters, so it only marginally compensates for the gap.

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?

States a specific verb+resource ('Connect the package to the GitHub release workflow') with the key mechanism (OIDC, no stored tokens). The action is distinctly not publish_package, add_workflows, or login, and an agent can tell what it accomplishes without opening the schema.

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 explains the per-registry flow and implies it is the OIDC alternative to stored tokens, but never states when to choose this over alternatives (e.g., vs login/token setup) or any when-not conditions. Usage is implied rather than explicit.

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