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

Annotations already mark the operation as readOnly, idempotent, and non-destructive, and the description adds no contradictions. Beyond that, it clarifies output freshness and completeness: it exposes each publisher's jurisdiction, language, reachability method, search eligibility with china_news_search, and recency of the latest indexed article. It does not discuss pagination or response limits, but for a 106-item read-only listing the outlined return contract is substantial.

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 a single dense sentence that front-loads the action and resource, then packs only high-value specifics: count, per-publisher attributes, and the strategic pre-search purpose. There is no filler or repetition of schema details.

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 compensates by spelling out exactly what fields each returned outlet carries and even gives the total count. Combined with 100% schema coverage for parameters and strong annotations, an agent has everything needed to decide whether to call this tool and what filters to use.

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 100%: the three optional filters (method, region, searchable_only) already have clear definitions and the region description explicitly distinguishes jurisdiction from language. The tool description primarily conveys output scope and pre-search usage, not additional parameter semantics, so it does not lift the score above the schema-only baseline.

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 a specific verb and resource: 'List the Chinese, Hong Kong, Taiwanese and overseas-Chinese news publishers Pipeworx has audited,' and pins the scope to 106 publishers. It enumerates the per-publisher fields returned and differentiates itself from china_news_search by showing what coverage actually exists before searching.

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 explicitly instructs an agent to call this tool 'before searching to see what coverage genuinely exists, instead of inferring it from an empty search result.' This names the workflow and the misleading alternative, giving a clear when-to-use signal without needing to open the schema.

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