get_sector_news

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

Description indicates a read-only operation fetching news, but lacks detail on output format, pagination, rate limits, or time range. With no annotations, the description partially carries the transparency burden but remains somewhat vague.

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 concise sentences plus a clear example. Every sentence serves a purpose with no redundancy, front-loaded with core functionality.

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 tool with 2 parameters and an output schema, the description covers core purpose and parameter usage. It could mention output format but output schema exists. Missing details like rate limits or required authentication but acceptable given simplicity.

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 has 0% coverage, so description adds value by providing example usage and listing possible sector values (IT, Banking, Pharma, etc.). The example clarifies the limit parameter's role, though a full list of sectors is absent.

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?

Description clearly states the tool retrieves latest news for a sector, with examples of sectors like IT and Banking. It effectively distinguishes from siblings such as get_market_news and get_stock_news by specifying sector focus.

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 implicitly guides usage for sector-specific news but does not explicitly contrast with alternatives like get_market_news or get_stock_news. No 'when-not-to-use' or prerequisite information is provided.

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