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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no restatement. The description adds genuinely new behavioral information beyond annotations: results are popularity-ordered, each clip carries a trending rank, and the remaining fields match search results.

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?

Two short sentences with zero filler, and the most important fact (what the feed contains and its ordering) is front-loaded.

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 explains the return shape (rank plus the standard search-result fields) and the sort order. The one gap is that the trending window behind 'right now' is never defined, which matters for a trending endpoint, but otherwise it is sufficient to call the tool 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?

Both parameters are fully documented in the schema (limit with default and max, cursor as nextCursor for paging), so the schema carries the semantics. The description adds nothing about limit or cursor behavior, which is acceptable given 100% coverage but earns only baseline credit.

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 states the resource (trending green screen clips in the Green Screen Memes app) and the ordering (most popular first, rank 1 = most popular). It is clearly a distinct feed from search_green_screens, though the verb is carried mainly by the title rather than the description text.

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 phrase 'what people are using right now' implies this is the tool for discovering popular content rather than querying by keyword, but it never names search_green_screens or states an explicit condition for choosing between them. Usage is implied, not spelled out.

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