get_latest_finance_news

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

With no annotations, the description carries the full burden of explaining behavior. It states that the tool fetches from RSS feeds and returns a list of articles, implying a read-only operation. However, it does not explicitly confirm read-only status or disclose potential side effects, error conditions, or rate limits.

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 a well-structured docstring with a one-line summary, Args section, and Returns section. It is concise, with every sentence adding value, and lists source options compactly.

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?

The description covers the tool's purpose, parameters, and return format, which is sufficient for a simple RSS-fetching tool with no required parameters. It lacks a brief note on error handling or source availability, but otherwise is complete enough given the low complexity.

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 description fully explains both parameters: 'limit' (maximum number of articles) and 'source' (with a list of allowed values like bloomberg, wsj, cnbc). This adds significant meaning beyond the schema, which only specifies type and default.

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 'Get the latest finance news from RSS feeds,' which is a specific verb ('Get') and resource ('latest finance news from RSS feeds'). This distinguishes it from the sibling tool 'search_finance_news' by emphasizing 'latest' rather than search.

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 provides no guidance on when to use this tool versus the sibling 'search_finance_news.' It does not mention any alternatives, exclusions, or conditions for use, leaving the agent without explicit context for tool selection.

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