get_news

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

No annotations provided, so the description carries the full burden. It discloses that symbols are required for stock and press modes, and that general mode ignores symbols. While it doesn't cover rate limits or error handling, the operational behavior (modes and parameter dependencies) is clear. No contradictions with annotations (none exist).

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?

Extremely concise and well-structured: a one-sentence purpose, a bulleted list of modes, and a note about an alternative tool. Every sentence adds value and the description is front-loaded with the most important information.

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 the presence of an output schema (stated in context signals), the description does not need to explain return values. With 7 parameters fully described in the schema, the description covers usage modes and alternatives, providing sufficient context for an agent to select and invoke the tool 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?

Schema description coverage is 100%, so baseline is 3. The description adds minimal extra meaning beyond the schema; it summarizes modes and symbol requirements, but the schema already documents all parameters comprehensively with detailed descriptions.

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 'Fetch news articles for stocks or the broad market' and enumerates three specific modes (stock-specific, general market, company press releases). It distinguishes itself from the sibling tool get_portfolio_news by noting the portfolio alternative.

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 describes the three modes and when to use each, including the requirement of symbols for stock and press modes. Provides a direct alternative tool (get_portfolio_news) for portfolio-aware auto-fill, guiding the agent away from this tool in that context.

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