douyin_browser_sync_if_needed

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

No annotations are provided, so the description carries the burden. It indicates the tool is conditional and syncs data, but does not disclose authentication needs, rate limits, or side effects beyond the implied cache expiration logic.

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?

Single sentence with no wasted words. However, it could be structured more clearly with explicit parameter references.

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?

Despite an output schema existing, the description omits explanations for 4 parameters with no schema descriptions. It lacks details on parameter semantics and usage context, making it insufficient given the complexity.

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 0%. The description hints at 'scope' through 'list, details, or all', but does not explain 'mode', 'recent_limit', or 'max_age_hours'. Partial value for scope, but insufficient for other three parameters.

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 tool syncs data (list, details, or all) when cache expires after confirming platform risk. It gives a specific verb and resource, but does not explicitly distinguish it from sibling sync tools like douyin_browser_sync_creator_data, though the scope 'list, details, or all' partially differentiates.

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 mentions conditional execution ('after confirming platform risk' and 'only when cache expires'), providing implicit guidance on when to use. However, it lacks explicit when-not-to-use instructions or comparison to alternative sync tools.

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