Central Bank news

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior. The description adds useful behavior beyond that: results are newest first, only titles are returned here, the filter matches titles, and dates are Jalali. It does not cover pagination behavior or rate limits, but the key operational traits 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?

The description is front-loaded with what the tool returns, then adds usage examples, the title-only limitation, the full-text alternative, ordering, filtering advice, and date format. Every sentence contributes actionable information without unnecessary verbosity.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does: titles, dates, ids, newest-first ordering, and title-only scope. Combined with complete schema parameter descriptions and safety annotations, an agent has enough context to call 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 coverage is 100%, so the schema already documents year, limit, and query. The description still adds meaningful semantics: the query parameter filters titles and short Persian root words are recommended, and it reinforces the Jalali date context. Limit behavior is left entirely to the schema.

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 states a specific verb and resource: it lists the Central Bank's latest news and announcements, including which fields are returned (title, date, id). It also explicitly distinguishes itself from cb_news_item by saying this tool provides titles only and the sibling provides full text.

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?

It gives clear usage context: find official statements on topics like liquidity, inflation, currency supply, bond auctions, and rules. It also names the alternative explicitly: use cb_news_item with an id for full text. The title-filtering tip is directly actionable.

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