list_ticker_news

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does at a high level ('Get recent news articles') without explaining what 'recent' means, whether there are rate limits, authentication requirements, pagination behavior, error conditions, or what format the news articles are returned in. This is inadequate for a tool with 6 parameters and no output schema.

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 extremely concise - a single sentence with no wasted words. It's front-loaded with the core purpose. While it's under-specified, what's there is efficiently stated without redundancy or unnecessary elaboration.

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 complexity (6 parameters, 0% schema coverage, no annotations, no output schema), the description is completely inadequate. It doesn't explain what the tool returns, how to use its parameters, what constraints exist, or how it differs from sibling tools. For a data retrieval tool with multiple filtering/sorting parameters, this minimal description leaves the agent guessing about critical usage details.

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 description coverage is 0%, meaning none of the 6 parameters have descriptions in the schema. The tool description provides no information about any parameters - it doesn't mention 'ticker' (the most critical parameter), 'limit', 'order', 'sort', 'published_utc', or 'params'. With 6 undocumented parameters, the description fails completely to compensate for the schema gap.

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 'Get recent news articles for a stock ticker' which provides a clear verb ('Get') and resource ('news articles for a stock ticker'), but it lacks specificity about scope or format. It doesn't distinguish this tool from potential sibling news tools like 'list_benzinga_news' or other list_* tools that might also retrieve news-related data.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools (over 50), including several news-related tools like 'list_benzinga_news', there's no indication of when this tool is appropriate versus those alternatives, nor any prerequisites or constraints mentioned.

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