Patch Node.js vulnerabilities

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false), so the description carries the behavior burden and does so thoroughly. It explains the PR flow, that merging triggers deployment, that non-patchable IDs are skipped, that an all-non-patchable selection is rejected, that only one patch PR can be open at a time, and the 404/403/422 failure modes.

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 information-dense but every sentence earns its place: core mechanics first, then prerequisites and failure modes, then edge cases and plan availability. Nothing is redundant, and the most important action is front-loaded.

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?

For a mutating tool with no output schema, the description is unusually complete. It covers prerequisites, permission requirements, error conditions for common failure cases, partial-success behavior, concurrency constraints, and plan eligibility. An agent has enough context to invoke it correctly and interpret the likely outcomes.

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%, so the baseline is 3. The description adds meaningful context on vulnerability_ids: only is_patchable vulnerabilities are patched, non-patchable ones are skipped, and the resulting PR's patch set is reported in patched_vulnerability_ids. It does not deeply explain username/domain, but the schema labels them acceptably and the overall semantics are clear.

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 opens with a specific verb and resource: 'Patches the selected Node.js vulnerabilities by updating the affected package versions in package.json and opening a GitHub pull request.' This clearly distinguishes it from list-only or deployment tools in the sibling set, such as hosting_listNode_jsVulnerabilitiesV1.

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 gives explicit when-to-use and when-not-to-use guidance: it only works for GitHub-connected repositories, archive-deployed sites return 404, the GitHub App needs write access, and only patchable vulnerabilities can be included. It does not explicitly name an alternative tool, but the conditions are concrete and actionable.

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