Download a certificate or a report

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

Annotations mark this as non-read-only and non-idempotent, and the description adds meaningful behavioral detail: the tool waits for the portal job, stores the file on disk, and returns the stored file path. No contradiction with the annotations.

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, prerequisite, behavior, and return value are all covered in two sentences with no wasted words.

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?

With an output schema and annotations present, the description covers the key prerequisite, waiting behavior, side effect of storing to disk, and return value. It does not discuss error cases or contrast with download_url, but nothing critical is missing for correct invocation.

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 key and target_dir are already documented in the schema. The description reinforces that key comes from hisinone_list_documents but adds little semantic value beyond what the schema provides.

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 uses a specific verb ('produce and store on disk') and identifies a single portal document as the resource. It distinguishes itself from hisinone_list_documents by telling the caller to call that tool first, but it does not explicitly differentiate itself from sibling hisinone_download_url.

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 gives an explicit precondition: call hisinone_list_documents first to get a key. This is clear usage guidance, though it lacks explicit exclusions or a direct comparison with alternatives like download_url.

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