fetch_creator_images

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

With no annotations, the description discloses real behavior beyond structure: default is fast account-only retrieval with no semantic/visual filtering, filter_mode=optional degrades when the local model is unavailable while required fails closed, downloads are bounded by max_posts/max_images, and resume=true continues pending media. It omits auth/rate-limit and on-disk overwrite behavior, but the safety/fallback semantics are well covered.

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?

Long but dense and front-loaded: platform/identifier rules come first, then media_type and filtering behavior, then bounds and resume. Nearly every sentence carries an actionable constraint, though it could be tightened slightly.

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 22-parameter tool with no annotations, the description covers the main selection workflow, fallback logic, and bounding parameters; return values need not be explained since an output schema exists. The remaining gap is the undocumented minority of parameters (time range, quality, concurrency, safe mode).

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% across 22 parameters, so the description must compensate. It meaningfully explains creator_id, creator_name, profile_url, media_type, content_query, filter_mode, max_posts, max_images, and resume, but leaves sort, since, until, cursor, min_width/min_height, output_dir, quality_mode, max_concurrency, include_video_covers, safe_mode, and download completely undocumented.

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?

States a specific verb and resource (download creator media), names the three platforms, and explicitly rules out a wrong interpretation ('NOT a post ID'), which helps place it against sibling tools like search_images/inspect_item.

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?

Gives explicit per-platform identifier rules (creator_id/handle/UID/sec_uid, creator_name, profile_url), a concrete fallback ('retry with the complete douyin.com/user/<sec_uid> URL because it is more stable'), and selection guidance for content_query and filter_mode.

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