get-instance-metadata

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

No annotations provided, so description carries full burden. Discloses conversion to text and non-image nature, but does not mention permissions, rate limits, response size, or error behavior. Adequate for a read-only retrieval tool, but lacks depth for complete transparency.

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?

Two sentences with no filler. First sentence states core function; second provides prerequisite and limitation. Every word earns its place.

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 3 parameters all documented, no output schema, and sibling tools listed, description covers what the tool does, its inputs, and what it doesn't do. Missing output format details, but for a conversion tool, this is acceptable. Overall, sufficiently complete for agent selection.

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 covers 100% of parameters with descriptions including examples and source instructions. Description adds context that UIDs come from find-instances, reinforcing schema. Since schema does most work, description still adds value, earning above baseline 3.

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 uses specific verb+resource: 'Retrieves and converts a DICOM instance to human-readable text.' Clearly distinguishes from siblings like render-instance-frame (image) and get-structured-report-text (structured reports) by stating it does not retrieve image data.

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?

Explicitly states prerequisite: 'Requires Study, Series, and SOP Instance UIDs from find-instances.' Also clarifies limitation: 'Does not retrieve image data.' Lacks explicit mention of when to use alternative tools like get-structured-report-text, but context is clear enough for selection.

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