download_note_images

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

Since no annotations are provided, the description carries full responsibility for behavioral disclosure. It specifies the local save path, automatic compression, inclusion of carousel images, and a critical access requirement (xsec_token). While it doesn't touch on authentication or error handling, the '重要' warning adds valuable context beyond what the schema alone offers.

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 concise and well-structured: it states the primary action first, then the scope, compression, and an important prerequisite. Each sentence contributes necessary detail without redundancy or fluff, making it easy to parse quickly.

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?

Given the absence of an output schema and annotations, the description covers the return value (file path list), side effects (local save, compression), and critical input constraints. It lacks edge-case behaviors such as failure modes or authentication requirements, but for a straightforward download tool, it provides sufficient contextual coverage.

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?

The schema provides complete descriptions for all four parameters, giving 100% coverage, so the baseline is 3. The description's only parameter-related remark—the need for xsec_token—mirrors the schema's own noteUrl description, adding no new information beyond what is already structured.

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 clearly states the tool downloads all images of a note, saves them to a specific local directory, and returns a list of file paths. This is a specific verb+resource+outcome that distinguishes it from sibling tools which handle searches, favorites, and content retrieval. The additional note about including carousel images further clarifies the exact scope.

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 provides a clear prerequisite: noteUrl must be a full URL with an xsec_token parameter sourced from get_favorites_list or search_notes_by_keyword. This tells the agent when and how the tool should be used, though it does not explicitly mention when not to use it or name alternative tools.

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