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

This description is highly transparent regarding execution behavior. It specifies the `wait_seconds` constraint (up to 120) and explains the logic of the results, specifically how the `pending` status operates and that the agent should proceed with available results immediately.

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 dense and long, making it slightly less concise than a list of bullet points, but it avoids redundancy by packing necessary information (input scope, output format, timing) into a single flow.

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, the description is extremely complete. It meticulously outlines the data returned for different content types (video summary vs. image content), covering all aspects of the tool's function from initiation to result.

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?

Although schema coverage is 0%, the description provides critical context for all parameters by explaining what types of identifiers (`ids` and `uuids`) are used. It specifically mentions the upper bound (120) for the `wait_seconds` parameter, adding semantic constraint beyond the schema type/default.

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 identifies the function as content analysis of queued TikTok posts, specifying that it provides status and results for both video and image posts. It differentiates itself by focusing on the analysis of pending items rather than just listing general trends.

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?

While it doesn't name alternatives, it sets a very clear scope: use this tool when you need status and summary data for currently queued posts. The note about continuing with what is done rather than waiting for the rest is a crucial operational guide for agent execution.

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