get_clinical_document

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that the tool downloads a PDF and, importantly, returns the file path where it was saved—a side effect an agent needs to know. It doesn't cover error behavior or file cleanup, but the key download-and-save behavior is transparent.

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 compact and front-loaded: purpose first, then parameter explanation, then return value. Every sentence earns its place, and there is no redundant boilerplate.

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 single-parameter download tool, the description covers the necessary call context: what it does, where the ID comes from, and what it returns. The main omission is any mention of failure modes or authorization requirements, which are not critical for a straightforward download but would make it fully 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?

Schema description coverage is 0%, so the description must fully explain the parameter. It does: doc_id is defined as 'The document ID from list_clinical_documents' with an example format ('12345'). This is exactly the kind of semantic enrichment the schema lacks.

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 opens with a specific verb ('Download'), a specific resource ('clinical document PDF'), and a clear discriminator ('by its ID'). It immediately distinguishes this tool from list_clinical_documents (listing vs. downloading) and from other get_* siblings (prescriptions, invoices).

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 explicitly says the doc_id comes from list_clinical_documents, establishing the workflow prerequisite (list first, then download). It does not name alternative tools to avoid, but the source guidance and tool name make the intended context clear.

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