Live Info

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

Annotations declare readOnlyHint=false, which could mislead an agent into assuming a mutation; the description resolves this by explaining it is a read-like POST with no publishing to social platforms. It also discloses paid credit consumption and the confirm gate. It does not cover rate limits or failure modes, so not a full 5.

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 action and sibling differentiation, then prerequisites, then cost warnings. Dense but each sentence carries information; the return-field enumeration slightly bloats an otherwise tight definition.

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 compensates by listing the fields returned, and it fully covers the prerequisite chain, cost model, and confirm requirement. An agent needs nothing else to invoke it correctly.

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 coverage is 100% and each parameter already documents its own origin. The description restates the room_id/user_id provenance paths but adds no syntax, format, or edge-case meaning beyond the schema, so the baseline 3 applies.

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 ('Gets curated room-level info for a TikTok live') and immediately distinguishes itself from the similarly named sibling /v1/tiktok/user/live by naming both the upstream difference and the reduced field set returned.

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 prerequisite ordering: call /v1/tiktok/user/live first for room_id, /v1/tiktok/profile first for user.id, and notes confirm=true is required for the credit-consuming call. This is a full when-and-how recipe rather than an implied context.

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