Get News Sources

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

The readOnlyHint annotation already indicates a safe read operation, and the description's 'List' wording is consistent with that. It adds minor context with 'from IB', but no additional behavioral details such as return format, ordering, or caching are provided. This meets the minimum baseline for annotation-backed descriptions.

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 single, front-loaded sentence with no wasted words. It immediately states the verb and resource, making it highly scannable and efficient.

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 zero-parameter tool with a read-only annotation, the description adequately explains the purpose and expected result (a list of sources). It lacks explicit return structure, but the phrasing 'List available...' implies a list of names or identifiers, which is sufficient for this simple tool. No major gaps 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?

With zero parameters, the description has no semantic burden for parameters. The baseline of 4 is appropriate since there is nothing to explain, and the description correctly focuses on the tool's action and result.

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 uses a specific verb 'List' and identifies the resource as 'available news sources/providers from IB'. This clearly distinguishes it from sibling tools like get_news_briefing, which handles news content rather than source listings.

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 implies usage for retrieving available news providers, but it does not explicitly state when to use this tool versus alternatives or mention any exclusions. For a zero-parameter listing tool, the use case is fairly obvious, but the lack of explicit guidance prevents a higher score.

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