snap_install

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

Annotations already provide idempotentHint=true and destructiveHint=false, and the description adds little beyond the basic 'install' action and a return string. It does not disclose side effects, permission requirements, or remote execution behavior, so it fails to add meaningful behavioral context beyond the annotations.

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 short and front-loaded, but the Args line mostly repeats information already present in the input schema. It is concise yet under-informative, and the terseness prevents it from covering usage context.

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 tool with siblings like apt_install and snap_remove, plus remote-host options in the schema, the description is too minimal. It does not explain when this tool is appropriate, what happens on the target host, or how the output should be interpreted.

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?

With schema description coverage reported at 0%, the description should compensate by explaining parameters, but it only lists their names: packages, host, response_format. It does not clarify which are required, what formats are expected, or that the schema reuses AptPackagesInput for a snap operation.

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 states 'Snap csomag telepitese' (Snap package installation), identifying a specific action and resource. It is clear about what the tool does and the 'Snap' qualifier separates it from apt-based sibling tools, though it does not explicitly contrast them.

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 snap_install instead of apt_install, apt_upgrade, or snap_remove. The description does not mention prerequisites, remote-host considerations, or exclusions, so an agent receives no decision support for choosing this tool.

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