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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine behavior beyond that: the returned counts are a floor ('over the >=3-network confirmed layer') and China is under-counted due to the GFW anomaly — meaningful data caveats an agent should know before trusting the numbers.

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?

Purpose is front-loaded in the opening clause and the caveat is clearly flagged with 'HONEST'. However the middle sentence is a dense three-clause run-on about domain/block/country counts that could be tightened; it is information-rich but bordering on verbose.

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 parameters, no output schema, and structured fields covering the safety profile, the description fully describes what the tool returns (human names, domain counts, confirmed-blocked counts, country counts) and the constraints on those numbers. Nothing needed to call it correctly is missing.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to disambiguate on the input side.

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 and resource ('maps every category code ... to its human name') and enumerates example codes (NEWS, POLR, HUMR...). The scope (a legend/reference table) is unmistakably distinct from siblings like get_category_coverage or get_category_leaders, so an agent can select it without opening a schema.

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?

Explicitly names when to reach for it: 'The reference for interpreting any category code returned by get_category_leaders, get_censorship_intent, or the national blocklist.' This routes the agent from three sibling tools to this one with a clear condition.

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