get_news

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

Discloses refresh frequency (every 30 min), source count (40+ trade sources), and return fields. readOnlyHint annotation is consistent with read-only nature. No contradictions.

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?

Three informative sentences, no wasted words, front-loaded with key purpose. Efficiently structured.

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?

Despite 7 parameters and no output schema, the description covers return values, usage context, and alternatives. The only minor gap is the parameter naming mismatch, but overall it is thorough enough for an agent to use correctly.

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?

Adds meaning beyond schema by mentioning filtering by topic and providing example usage, but has a mismatch: description uses 'topic' while schema has 'category'. With 0% schema coverage, description partially compensates but not for all 7 parameters.

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?

Clearly states it retrieves curated data center industry news from 40+ trade sources. The verb is implied (get/list) and the resource is well-specified. Distinguishes from siblings like list_transactions and get_pipeline.

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?

Explicitly says when to use ('Industry news only') and when not to use ('do NOT use for structured M&A deal data or construction pipeline'), naming specific alternative tools (list_transactions, get_pipeline). Also provides an example query.

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