Send a photo carousel to the TikTok inbox

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

Annotations already cover read-only, idempotency, and destructiveness, so the description only needs to add context. It adds useful behavioral facts: the creator must finish in the app, the request needs only the video.upload permission, and TikTok rejects the request if the app version is below 31.8. This is meaningful and goes beyond what annotations and schema provide.

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 three short sentences with no filler. The core action is front-loaded, followed by the permission requirement and the version constraint, each of which earns its place. It is easy to scan and directly actionable.

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?

The description is adequate for understanding the basic operation and key constraints, but it leaves gaps because there is no output schema and no explanation of parameter meaning or async/result behavior. An agent can probably invoke it correctly but may not know how to interpret the response or how it relates to send_video_to_drafts and post_photos.

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 only 20%, with only the account parameter described. The description does not explain photo_urls requirements, photo_cover_index semantics, or how title and description are used. Because the schema leaves most parameters undocumented and the description does not compensate, an agent has to guess about important invocation details.

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 action, resource, and destination: send photos to the TikTok inbox for the creator to complete. The phrase 'for the creator to finish in the app' also distinguishes this from direct publishing, and the photo focus separates it from send_video_to_drafts. The title reinforces the photo-carousel scope without adding misleading information.

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 implies the tool is for preparing photo content as drafts rather than publishing it, and it gives valuable prerequisites such as the video.upload permission and TikTok app version 31.8+. However, it never explicitly names alternatives like send_video_to_drafts or post_photos, nor does it state when not to use this tool.

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