synology_get_packages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply says 'List installed packages' without mentioning whether the operation is read-only, requires special permissions, or what the returned data looks like. While 'List' implies a non-destructive query, this is not explicit and no additional behavioral context is given.

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 one concise, front-loaded sentence that states exactly what the tool does with no filler or redundancy. Every word contributes to meaning, making it highly efficient.

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 simple single-parameter list operation, the description is largely sufficient for invocation: the agent knows the input and the action. However, without an output schema or any indication of return structure, and with weak behavioral transparency, the context is not fully complete. It's adequate but has clear gaps.

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?

The schema covers the single parameter 'device_id' with a clear description ('Synology NAS device ID'), and the tool description adds no further parameter-level detail. Since schema description coverage is 100%, the baseline of 3 is appropriate; the description does not enhance understanding of the parameter beyond the schema.

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 the action ('List') and the resource ('installed packages') on a Synology NAS, making the tool's purpose unambiguous. It distinguishes itself from sibling tools like synology_get_storage or synology_get_network by focusing specifically on packages, though it doesn't explicitly differentiate from similar tools like synology_get_docker.

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 implies usage when one needs to see installed packages on a Synology NAS, but offers no explicit guidance on when to prefer this over alternatives, nor any prerequisites or exclusions. The intended use case is fairly obvious from the name and description, so it meets the 'implied usage' level but nothing more.

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