get_image

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

With no annotations provided, the description carries the full behavioral burden. It does declare the operation is read-only ("只读"), which is a meaningful trait, but says nothing about rate limits, auth, caching behavior, or what the returned download address looks like or how long it is valid.

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?

A single front-loaded sentence plus two short clauses: purpose, parameter constraint, and safety profile, with zero filler. Nothing is wasted.

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 simple two-parameter read tool with 100% param coverage and no output schema, the description covers what it returns (image info and download URL), how to call it, and that it is read-only. The main residual gap is that the format/lifetime of the returned download address is not addressed.

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 coverage is 100%, so the baseline is 3, but the description adds real value beyond the schema: it clarifies the either/or relationship ("传一个") that the schema alone does not convey, since both properties are optional with no required fields. It does not restate the schema's own hint that file_id is preferred.

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 specific verb and resource: retrieve image info and a download address ("取图片信息与下载地址"). It is the only image-oriented tool among the siblings, so it is naturally distinguishable, though it does not explicitly contrast itself with any alternative.

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?

It gives invocation guidance ("file 或 file_id 传一个" — supply one of the two), which is useful since no parameter is marked required. However, it offers no when-to-use context, no prerequisites, and no mention of any alternative tool or condition under which to prefer one identifier over the other.

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