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

With no annotations and a description that only says 'Get popular videos,' there is no disclosure of read-only status, pagination behavior, rate limits, or return format. The description fails to convey any behavioral trait beyond the implied read operation.

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?

'Get popular videos' is brief and front-loaded, but it is under-specified to the point of being uninformative. This is an instance of under-specification rather than effective conciseness, as the phrase adds no value beyond the name.

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?

The tool has 4 parameters, no output schema, and no annotations, yet the description offers no explanation of popular criteria, default period, pagination, or return values. This is completely inadequate for the tool's 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 100% with each parameter (page, period, orderBy, countryCode) having a description, so the baseline is 3. The tool description adds no additional parameter context, but the schema already handles the semantic burden.

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 'Get popular videos' is a direct restatement of the tool name and provides no platform, source, or definition of 'popular.' It fails to distinguish this from sibling tools like scrapecreators_get_popular_creators or scrapecreators_get_popular_songs.

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?

No guidance is provided on when to use this tool versus alternatives. The description gives no context about suitable scenarios, prerequisites, or advantages over any of the many sibling get_* and scrapecreators_* tools.

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