get_latest_news

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

With no annotations provided, the description carries the behavioral disclosure burden. It reveals that include_url defaults to false to save tokens, sets a maximum limit of 1000, and advises the agent to show all data by default. These details go beyond the schema, though it does not mention side effects or rate limits.

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, followed by a clean Args/Returns structure and a concise bulleted list of display suggestions. Every section adds value without unnecessary verbosity.

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?

The tool is simple with 3 parameters and an output schema, and the description covers purpose, parameters, return type, and usage tips. It lacks explicit ordering guarantees or empty-result behavior, but it is adequate for a straightforward fetch tool.

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 0%, but the description thoroughly explains all three parameters: platforms with an example list, limit with default and max, and include_url with its token-saving rationale. This fully compensates for the schema's lack of descriptions.

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 '获取最新一批爬取的新闻数据' (get the latest batch of crawled news data), clearly stating the verb, resource, and temporal scope. It distinguishes itself from siblings like get_latest_rss by specifying news data, and it conveys the purpose of quickly understanding current hotspots.

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 provides clear context for when to use the tool by focusing on the latest crawled news, and it includes explicit display guidance on showing all data unless the user asks for a summary. However, it does not explicitly list alternative tools or when-not-to-use scenarios.

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