Search News

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful behavior context by noting that it works in Bengali or English and that it performs a search rather than a mutation, but it does not disclose details like rate limits, result handling, or pagination.

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, with two short sentences and a purpose statement. Every sentence adds value: the first states the operation and resource, the second clarifies language support and intended use.

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 is largely complete for a two-parameter search tool: it explains the query, the source, language support, and intended use case. An output schema exists, so return value details are covered. It would be slightly stronger with explicit sibling differentiation or an explanation of the limit parameter.

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 adds meaning by explaining the query is a keyword search and supports Bengali or English, which clarifies the query parameter. However, the optional limit parameter is not addressed in the description, leaving that meaning solely 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 names a specific verb and resource: 'Search Prothom Alo articles by keyword.' The use case of tracking a topic, brand, person, or event makes its purpose unmistakable and clearly distinct from siblings like latest_news or list_sections.

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 explicitly states when to use the tool: for tracking a topic, brand, person, or event in Bangladeshi media. It does not mention when not to use it or name alternatives, but the use case is clear enough to guide selection.

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