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

readOnlyHint=true already establishes the safe-read profile, and the description adds genuinely new behavioral detail: the URL is temporary, and XML/CDA files can be converted to html or pdf. It omits expiry duration and any auth requirements on the returned URL, so it is helpful but not exhaustive.

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?

One front-loaded sentence carries the purpose, input, and optional conversion behavior. The trailing "Medical API: GET /medical/v1/document/download-url" is mildly redundant with the tool's title but aids endpoint alignment.

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?

No output schema exists, yet the description adequately characterizes the return value (a temporary download URL). For a 2-parameter read tool with readOnlyHint coverage, the missing details are minor: expiry window and any auth needed to fetch the URL.

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%, so both parameters are already documented in the schema. The description's mention of optional XML/CDA-to-html/pdf conversion largely restates the conversionType schema text; no syntax, defaults, or format constraints are added beyond it.

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?

States a specific verb (get), a precise resource (temporary downloadable URL for a document), and the lookup key (file name). This is clearly distinguishable from sibling list_documents, which enumerates files rather than producing a download link.

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 names the prerequisite source for the required input ("file name ... from metriport_list_documents"), which routes the agent correctly. It stops short of stating when-not to use it or naming a direct alternative, so it lands at clear-context without exclusions.

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