Download a portal file by address

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

Annotations already signal readOnlyHint=false and idempotentHint=false, so the description is not the sole source of behavioral context. It adds that the operation stores a file locally and requires the URL to be portal-scoped, which is useful. However, it does not describe overwrite behavior, naming conventions, or side effects beyond 'store one file'; still, the annotation bar lowers the burden and no contradiction exists.

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 two sentences with no filler, and the example is front-loaded into the first sentence. The only minor issue is that 'Store' is slightly inconsistent with the title's 'Download', but overall the description is compact and efficiently structured.

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, full parameter descriptions, and annotations, most invocation details are already covered. The description is mostly sufficient for a simple three-parameter tool. The main completeness gap is the missing differentiation from the closely related sibling hisinone_download_document, which an agent would need to route correctly.

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 the schema already documents all three parameters and the baseline is 3. The description adds a meaningful semantic constraint ('The address must point at the portal') and a concrete example URL shape, but it does not add detail about filename or target_dir 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 states a concrete action ('Store one file that a portal page links to') and identifies the resource as an address-based portal file, with a concrete docId-in-URL example. It is clear on verb and resource, but it does not explicitly differentiate this from the sibling hisinone_download_document; the distinction is only implied by 'by address'.

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 a hard precondition ('The address must point at the portal') but provides no guidance on when to choose this tool over hisinone_download_document or any other sibling. There is no explicit when-to-use, when-not-to-use, or alternative-selection logic, so the agent must infer the intended use case.

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