install_rule_packInstall a previously imported rule pack to persist every included rule into the ProxyKit engine, activating multiple proxy rules at once.
Install a previously-imported rule pack. This persists every rule inside the pack into the engine — potentially many rules at once, so use with care.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Rule pack id from list_rule_packs. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly=false, destructive=false, and idempotent=false. The description adds useful context beyond them by warning that installation persists potentially many rules at once, but it doesn't clarify reversibility, whether existing rules are replaced, or permission requirements.
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?
Two short sentences, front-loaded with the core action and scope, with the caution attached at the end. Minimal waste, though 'use with care' is somewhat imprecise.
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 single-parameter tool with no output schema, the description adequately covers action, scope, and the bulk-effect caveat. It stops short of describing side effects on existing state or the expected result, but is otherwise complete.
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% and the single id parameter is fully documented with a pointer to list_rule_packs, so the schema carries the burden. The description adds no further parameter detail, making the baseline 3 appropriate.
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 (Install) and resource (rule pack), and the qualifier 'previously-imported' distinguishes it from the sibling import_rule_pack. An agent can tell what operation this performs and on what object.
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?
'Previously-imported' implies a precondition (import first), and 'use with care' suggests caution, but no explicit alternatives or when-not-to-use guidance is given despite siblings like import_rule_pack, list_rule_packs, and delete_rule_pack being available.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.