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

Annotations already declare readOnlyHint=true and openWorldHint=true, lowering the bar. The description adds meaningful behavioral detail: every result carries its score, price, and source; direction flips ordering; available_only restricts to buyable entities. This goes beyond the annotations and helps the agent understand what to expect from the call, though async behavior is left to the schema.

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 front-loaded with the core purpose, then covers criteria, direction, availability, and usage guidance in a compact paragraph. It is well-organized and not verbose, though it repeats some enum values from the schema (e.g., the criterion list), which is slightly redundant but not harmful.

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 an output schema present, the description need not explain return values in detail, but it does state that every result includes score, price, and source. It covers purpose, filtering options, direction semantics, and when to use the tool. The async parameter is not mentioned, but the schema covers it, so the tool is sufficiently complete for an agent to select and invoke 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?

Schema coverage is 100% with thorough descriptions for all parameters, including enum details for criterion and direction. The description reiterates the criteria ('critic_score, popularity, price, value') and adds usage examples, but it does not add new meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 opens with the specific verb 'Return the TOP-ranked content entities in a category, by a chosen criterion' and immediately ties it to superlative/decision queries with concrete examples like 'best video games' and 'top RPGs'. This clearly distinguishes it from sibling tools like content_discovery or content_compare, and the 'direct answer' phrasing reinforces its unique role.

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 includes an explicit 'When to use' section: 'an agent must produce a ranked shortlist to support a recommendation, a purchase or a "what is the best X" decision.' This provides clear context for when to invoke the tool, though it does not mention exclusions or name alternative tools, so it stops short of a full 5.

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