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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds behavioral context by stating the ordering is by readership rather than date, and that results are ranked over a specified window. It does not contradict annotations and provides useful non-obvious behavior beyond 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?

Two sentences, both information-dense. The first states the core function and scope; the second provides usage context and sibling differentiation. No filler or redundant detail.

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 simple read-only list tool with full schema coverage, an output schema, and helpful annotations, the description covers purpose, ordering, time window, and usage boundaries. All essential context is present, and the output schema handles return-value details.

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%; all parameters (lang, limit, period) already have clear descriptions including defaults and enum values. The description contributes only minimal interpretive value by connecting 'last day, week or month' to the period parameter and clarifying the sort intent, but it does not need to do more since the schema is comprehensive.

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 clearly specifies the action ('List'), the resource ('most-read Trend News Agency articles'), the time window ('last day, week or month'), and the ordering ('by readership rather than by date'). It also explicitly distinguishes itself from the sibling tool trendaz_news_list, making its purpose unambiguous.

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?

It provides an explicit use case ('what is Trend's audience paying attention to') and contrasts it with a different question ('what is the latest news') that belongs to trendaz_news_list. This gives concrete when-to-use and when-not-to-use guidance with a named alternative.

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