get_news

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

No annotations provided, so description bears full burden. Only parameter descriptions are given; no behavioral traits (e.g., read-only, rate limits, output format, or side effects) are disclosed.

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?

Concise docstring-style with parameter list. No redundant sentences, all information relevant. Slightly verbose due to formatting, but acceptable.

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?

Covers all 8 parameters with explanations. Output schema exists, so return value description not required. Lacks details on pagination behavior and sort_by accepted values, but sufficient for basic usage.

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?

Description adds meaning to each parameter (e.g., 'Comma-separated ticker symbols to filter by (e.g. AAPL,MSFT)'). Schema lacks descriptions, so this compensates well. Lacks clarification on defaults and null behavior.

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 states 'Search financial news articles from 50M+ sources' with clear verb (search), resource (news articles), and scope (50M+ sources). Distinct from sibling tools focused on financial data like prices and fundamentals.

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 explicit when-to-use or when-not-to-use guidance. Context is implied by domain (news vs financial data), but no alternative tools mentioned or exclusions given.

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