Live

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

Goes beyond the annotations by disclosing that the call 'potentially consumes paid API credits', requires confirm=true, and clarifies that read-like POST requests do not publish to social platforms — meaningful context given readOnlyHint=false and openWorldHint=true could otherwise look risky. It still doesn't say whether the result is cached or how fresh the live status is.

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?

Front-loaded with the core purpose, followed by the behavioral caveats. The long parenthetical enumerating every returned field (nickname, avatar, followerCount, roomId, title, startTime, status...) is somewhat heavy, but it earns place given there is no output schema.

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?

With no output schema, the description usefully enumerates the return payload, and it covers the credit/confirm behavior. The main gap is that it never positions itself against the similarly named tiktok_live_info sibling.

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 100%, so handle, account, and confirm are already documented in the schema; the description adds no further parameter detail. Per the rubric, baseline 3 applies when the schema does the heavy lifting.

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: 'Checks if a TikTok user is currently live streaming and retrieves their live room details.' Clear on its own, but it never distinguishes itself from the sibling tool tiktok_live_info, which by name appears to cover overlapping live-room territory.

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 gives usage guidance about the output ('use the top-level is_live boolean instead of checking TikTok's numeric status values yourself'), but that is about interpreting results, not about when to choose this tool versus tiktok_live_info or other live-related siblings. Usage context is implied only.

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