get_bbc_news

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

No annotations are present, so the description must fully disclose behavior. It states it '提供' (provides) news but does not specify whether it returns summaries, full articles, or if there are rate limits, pagination, or authentication requirements. This is a significant gap for a news-fetching tool.

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 sentence that is short and front-loaded with the purpose. It could be more structured but is not bloated. However, the list of categories is somewhat redundant with the schema.

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?

Given no output schema, no annotations, and only 2 parameters, the description is insufficient. It does not explain the response format, article count, sorting, or any additional context needed for effective 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?

The input schema has two parameters (category, edition) with enums and descriptions. The tool's description lists categories but adds no extra meaning beyond the schema. With schema description coverage at 50%, the description should compensate but does not explain parameter interaction or behavior when left empty.

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 states the tool retrieves BBC news and lists multiple categories (global, UK, business, politics, etc.). However, it does not distinguish itself from sibling news tools like get_nytimes_news or get_theverge_news, which also fetch news.

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?

No guidance on when to use this tool versus alternatives like get_nytimes_news or get_bbc_news is provided. The description lacks any context about suitability or exclusions.

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