polymarket_get_news

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It usefully mentions 'No API key required' and that it uses Google News RSS, but it does not disclose rate limits, potential latency, or the structure of returned data. This is adequate but lacks depth.

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 three short sentences, each adding distinct value: the core action, the use case, and the authentication note. There is no redundancy or filler, making it easy to parse quickly.

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 news-fetch tool with no output schema, the description covers purpose, use case, and auth, which are the key decision factors. However, it does not describe the return format (e.g., list of headlines with dates and links), which would help an agent anticipate results. This is a minor gap given the tool's 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?

The schema provides a description for 'query' with examples, but 'limit' has no description in the schema. The tool description does not explain what 'limit' controls, leaving a gap at 50% schema coverage. It adds no meaning beyond the schema's numeric constraints, so the description fails to compensate for the undocumented parameter.

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 a specific action ('Fetch recent news headlines for a topic via Google News RSS'), clearly identifying the resource and method. This distinguishes it from the trading/market siblings, which are all focused on Polymarket data or order operations.

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 explicitly states a use case: 'useful for understanding current events and market context when analyzing prediction markets.' This tells the agent when to use the tool, and the sibling list makes alternatives obvious, though it does not explicitly state when not to use it.

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