tickerbot_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 explains the archive depth, available columns, filter patterns, and aggregation support. It doesn't cover pagination or rate limits, but the schema covers cursor/limit, and the read-only nature is implied.

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 reasonably concise, with the main purpose front-loaded and only essential details included. The column list and examples are useful but make it slightly dense; still, every sentence earns its place.

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?

Given the tool's complexity (9 parameters, no output schema), the description covers the primary use cases well with examples and column details. It doesn't explain every parameter, but the schema fills that gap. It lacks explicit return-format info, but the column list compensates.

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?

The schema has 100% coverage of parameters, so the baseline is 3. The description adds meaning beyond the schema by explaining the SQL WHERE clause for q, providing example syntax, and mentioning group_by/having behavior, thus adding 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 'Search the news archive (back to 2015) with a SQL WHERE clause.' This uses a specific verb and resource, and distinguishes the tool from sibling tools focused on tickers, signals, or webhooks.

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 provides clear context on usage, including availability on every plan, SQL syntax, example queries, and aggregation support. It doesn't explicitly say when not to use this tool versus alternatives, but the description makes the use case clear.

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