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

Annotations (readOnlyHint=true, openWorldHint=false) already establish a safe read over a finite dataset, so the bar is lower. The description still adds real value by disclosing the ranking methodology and the honest composition caveat (gambling/piracy/adult dominating over political censorship), which annotations cannot convey.

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, front-loaded with purpose then the caveat, with zero filler. The 'HONEST:' framing is informal but functions as an effective signal to the agent; the description is neither bloated nor truncated.

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 carries return-value burden and does so adequately by describing the shape (a ranked leaderboard) and its typical contents. Pagination/limit behavior is left entirely to the schema, and the exact returned fields are unspecified, keeping it just short of fully complete.

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%, so baseline is 3. The description goes beyond the schema by explaining the semantic effect of specific category values (ANON isolates circumvention tools; NEWS targets news sites) and naming example domains, which the terse schema enum examples do not.

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 resource ('global leaderboard of the most-blocked domains') plus the exact ranking metric ('ranked by how many countries nationally block them'). An agent immediately knows this is a domain-level leaderboard distinct from country-level or category-level siblings.

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 strong interpretive guidance on what the default result contains and how to steer it ('use category=ANON ... or category=NEWS'). It does not, however, name the sibling tools (e.g. get_most_censored, get_category_leaders) that an agent might otherwise pick, so the routing guidance is contextual rather than comparative.

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