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

With no annotations, the description carries the full burden for behavioral disclosure. It only says 'retrieves media and metadata' without specifying what media or metadata includes, potential errors, authentication needs, or rate limits. The added 'Group' and 'Billing' info are not behavioral traits.

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 core sentence is concise and front-loaded with the primary function. However, it includes extra non-behavioral fields ('Group' and 'Billing per call') that are not strictly part of a behavioral description, slightly diluting focus, but it remains efficient.

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 lack of output schema and annotations, the description is insufficient to fully inform the agent about return contents or constraints. It is vague about what 'media and metadata' entails, and does not clarify URL format requirements or error conditions, making it incomplete for practical use.

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 input schema already provides a description for the URL parameter, and the tool description adds no additional meaning beyond restating that it's a 'given TikTok post URL'. Since schema coverage is 100%, the baseline is 3; the description does not go beyond that.

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 action ('Retrieves media and metadata') and the target resource ('TikTok post URL'), distinguishing it from sibling tools like get_tiktok_v3_user_details which target user details. It is specific and unambiguous.

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 no guidance on when to use this tool versus alternatives. It does not mention that this is for post details only, nor does it reference sibling tools or conditions. Usage must be inferred from the name alone.

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