get_news

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by noting the news is 'in the app language, TR_LOCALE', but it does not disclose return format, pagination, or any additional limits beyond the schema.

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 15-word sentence that front-loads the core purpose ('Recent news about an instrument') and adds the locale qualifier without any fluff or redundancy.

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 two-parameter read-only tool, the description conveys the core purpose and locale behavior, but because there is no output schema it leaves the return structure unspecified. It also does not clarify what 'limit' controls, which an agent would need for correct invocation.

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 0%, so the description must compensate for parameter meaning. It only loosely maps 'instrument' to the isin parameter and says nothing about the limit parameter's semantics, such as whether it caps the number of news items returned.

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 identifies the resource ('recent news') and the subject ('an instrument'), and the tool name supplies the verb. It distinguishes get_news from siblings like get_quote, get_price_history, and get_stock_details by data type, though it does not explicitly contrast with any sibling.

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?

Usage is implied through the purpose: an agent would call this when it needs recent news about an instrument. However, there is no explicit guidance on when to prefer get_news over related tools like get_stock_details or get_instrument, nor any exclusions.

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