pkg_install

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

No annotations are provided, so the description carries the full burden. It discloses auto-detection of package managers but omits critical behavioral traits like permission requirements (sudo), error handling, idempotency, output/return behavior, and potential destructive impact.

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 sentences are concise but severely under-specify the tool. Conciseness is achieved at the expense of necessary detail, making it borderline acceptable.

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 incomplete given the lack of output schema, annotations, and minimal parameter docs. It fails to explain return values (success/failure), error scenarios, or behavior for non-existent packages, which is critical for a state-changing tool.

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% (only 'packages' described). The description adds no additional meaning beyond the schema—it does not explain 'session_id' or elaborate on package naming conventions beyond the schema example.

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 'Install packages' identifying the action and resource. It distinguishes from sibling tools like pkg_list (listing) and pkg_update (updating), but lacks specificity about what 'install' entails (e.g., from repos versus local files, dependency handling).

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?

No guidance on when to use this tool versus alternatives like exec (manual install) or pkg_update. The description does not provide any context for appropriate use cases or exclusions.

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