pacs_study_summary

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

With no annotations provided, the description carries full burden. It clearly enumerates the four return components and uses 'Query' implying read-only behavior, but omits explicit safety declarations, error handling (e.g., study not found), rate limits, or whether the '[Premium]' label affects access/behavior.

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?

Front-loaded with the core action and well-structured with the '[Premium]' tag, main function sentence, return value enumeration, bridge metaphor, and input clarification. Slightly redundant in mentioning search parameters at the end since the schema already documents them, but overall efficient for the complexity described.

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?

Given the lack of an output schema, the description adequately compensates by detailing the four complex return structures (including specific message types like ORM^O01). However, it could improve by noting that at least one identifier is logically required (despite schema showing 0 required parameters) or describing error response behavior.

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 has 100% description coverage for both parameters ('Study Instance UID to look up' and 'Accession number to look up (alternative to UID)'). The description adds minimal semantic value beyond the schema, merely confirming 'Search by Study Instance UID or accession number' without adding format constraints, validation rules, 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?

Description explicitly states the tool 'Query[ies] a study from PACS and show[s] its complete interoperability mapping' and distinguishes from siblings by detailing four specific return components (metadata, DICOM-to-HL7 mapping, HL7-to-FHIR mapping, and HL7 ORM^O01 skeleton) that combine functionality of separate 'map_*' and 'pacs_*' tools into a single interoperability bridge.

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 implied usage context by describing itself as 'the bridge between what's in PACS and how do I represent it in HL7/FHIR', but lacks explicit guidance on when to choose this comprehensive tool over simpler alternatives like 'pacs_get_metadata' or the individual 'map_dicom_to_hl7' and 'map_hl7_to_fhir' tools.

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