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

With no annotations and no output schema, the description carries the full burden of disclosing behavior. It says nothing about what data is returned, how pagination works, whether it is a read-only operation, or any other behavioral trait. The description is a bare fragment that adds no transparency.

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 only three words long, but this is under-specification rather than effective conciseness. It is structurally a fragment without a sentence or any useful elaboration, so it does not earn the 'appropriately sized' criterion.

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 tool has 2 parameters, no annotations, and no output schema, the description should explain what the tool returns and how it works. The description provides none of this, making it completely inadequate for an agent to understand the tool's context or behavior.

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 covers both parameters (clipId and cursor) with 100% coverage, including a detailed example for clipId. Since schema_description_coverage is high, the baseline is 3, and the description adds no additional meaning, making it neither better nor worse than the schema alone.

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 'TikToks using Song' is a noun phrase that restates the tool name without a clear verb or action. It vaguely implies the tool returns TikToks that use a given song, but it lacks any verb such as 'get', 'list', or 'scrape' and does not clearly distinguish from sibling tools like scrapecreators_reels_using_song.

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. There are no context signals about use cases, exclusions, or comparisons to sibling tools. A user would have to infer usage 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.