synology_get_docker

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

With no annotations provided, the description carries the full burden. It implies a read-only operation via 'List', but it does not disclose any additional behavioral traits such as whether only running containers are shown (only 'running' is mentioned), pagination, authentication requirements, or return format. This is adequate for a simple read-only tool but not rich.

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 a single, concise sentence with no redundant words or unnecessary detail. Every word contributes to the meaning, making it perfectly scoped.

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 one-parameter tool with no output schema, the description covers the essential purpose well. It could optionally detail what information is returned for each container, but it does not leave the agent entirely in the dark. Given the low complexity, it is nearly 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?

The schema provides 100% coverage for the only parameter, device_id, with a clear description 'Synology NAS device ID'. The tool description does not add any further meaning beyond that, so the baseline of 3 is 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?

The description clearly states the specific action ('List Docker containers') and the target resource ('running on Synology NAS'). It distinguishes itself from sibling tools like synology_get_storage and synology_system_info by focusing solely on Docker containers.

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 someone needs a list of Docker containers on a Synology NAS, but it provides no explicit guidance on when to prefer this tool over others or any exclusion criteria. It is not misleading, but it lacks direct alternative differentiation.

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