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

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world behavior, so the safety profile is covered. The description usefully adds that results are sorted by likes and scoped to a window, but says nothing about pagination, result volume, or what an empty window returns. With annotations carrying the safety burden, a 3 is appropriate.

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 sentences with no padding, and the core behavior (best-performing posts sorted by likes in a window) is front-loaded before the usage guidance. Efficient, though it could tighten by pairing each trigger directly with the scoping it implies.

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?

For a two-parameter, all-optional read tool with no output schema, the description covers purpose, ranking, and usage triggers adequately. It does not describe the shape of returned posts (fields, count), which is a minor gap given no output schema exists to carry that.

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 description coverage is only 50%: limit only says 'Default 5.' and window exposes its enum values but no meaning. The description maps loosely to the window parameter ('in a time window') and mentions ranking, but adds no guidance on choosing a limit or interpreting the enum. Baseline 3 given the partial coverage.

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 (List) and resource (posts) with the ranking criterion (best-performing, sorted by likes) and scoping (time window). An agent can distinguish it from sibling readers like get_post or search_inspiration. It stops short of explicitly naming which sibling to prefer, so it is clear but not fully sibling-differentiating.

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 concrete user-intent triggers ('what worked', 'what went viral', 'examples of best content'), which is exactly the context an agent needs to route here. It does not state when NOT to use it or name an alternative like get_analytics or search_inspiration, so it is strong but not exhaustive.

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