news_search

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

No annotations are provided, so the description must carry the burden. It mentions relevance scoring with recency boost and credit cost, which are useful. However, it does not disclose output format, ordering, or pagination behavior, leaving gaps for an agent.

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?

A single, well-structured sentence covering purpose, filters, scoring, and cost. Every word adds information; no redundancy or fluff.

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 tool with 6 optional params and no output schema, the description covers the key behavioral aspects (scoring, cost) and filter options. It lacks output details but is sufficient for basic invocation decisions.

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 baseline is 3. The description only echoes the existence of filters (date range, provider, category) without adding deeper meaning beyond the schema's own descriptions. No significant added 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?

The description clearly states the tool performs full-text search on a specific corpus (TensorFeed news) and lists optional filters. While the purpose is clear, it does not explicitly distinguish from sibling tools like get_ai_news or whats_new, missing a chance for differentiation.

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 when to use (searching news articles with filters) but provides no guidance on when not to use or alternatives. Given the presence of other news-related sibling tools, clearer usage boundaries would help.

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