Latest News

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

With no annotations provided, the description carries the behavioral disclosure burden and does so well: it reveals that the API has no server-side section filter preserving recency, that section requests scan the newest 100 stories, and that quiet sections may return fewer items. It does not mention auth or rate limits, but these are not implied by the tool's simple read/list nature.

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 compact and front-loaded, leading with the core behavior, then providing needed parameter guidance and a single caveat. Every sentence adds value and there is no filler or unnecessary repetition of schema fields.

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 read-only listing tool with two optional parameters and an output schema, the description covers the core behavior, ordering, section discovery, and the key edge case of local filtering. Nothing necessary for correct invocation is missing.

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. It thoroughly explains `section` with example slugs and points to list_sections for valid values. `limit` is left to the schema, but its meaning is clear from the tool's purpose and default value.

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?

States a specific verb and resource ('Get the most recent Prothom Alo articles, newest first'), making the tool's function unambiguous. The ordering and scope clearly distinguish it from sibling tools like search_news and read_article.

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 offers clear context for the section parameter by instructing the agent to 'Call list_sections to see what exists.' It also explains the local-filtering behavior for sections, though it does not explicitly contrast latest_news with search_news or read_article.

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