pacs_retrieve

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

With no annotations, the description carries the full burden. It discloses network side effects ('moves real images across the network') and configuration prerequisites, but omits execution details like synchronous/asynchronous behavior, error handling, return values, or idempotency characteristics crucial for a network mutation operation.

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?

Four sentences with zero waste: front-loaded action ('Initiate C-MOVE...'), safety warning, protocol constraint, and configuration prerequisite. The '[Premium]' tag efficiently signals feature gating without verbosity.

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 complex network operation with side effects and no output schema, the description should describe success indicators or return behavior. It adequately covers prerequisites and safety but leaves the agent unaware of what constitutes successful invocation or failure modes.

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 100%, establishing a baseline of 3. The description mentions 'C-MOVE' which provides protocol context for the UID parameters, but does not add semantic details beyond the schema (e.g., AE title formatting rules, UID syntax constraints, or examples).

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 ('Initiate C-MOVE'), resource ('images from PACS'), and destination ('destination AE title'). Mentioning 'C-MOVE' specifically distinguishes it from sibling query tools like pacs_query (likely C-FIND) and pacs_echo.

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?

Provides explicit constraints ('Only available via DIMSE protocol', 'Requires DICOM_HL7_PACS_ALLOW_RETRIEVE=true') and safety warnings ('use with care'). Lacks explicit contrast with siblings (e.g., when to use query vs retrieve), but the technical prerequisites serve as clear usage gates.

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