get_news

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

With no annotations, the description must carry the burden of behavioral disclosure. It only says "fetches," which implies a read operation, but does not explain output format, pagination, rate limits, default behavior, or how filters interact. For a tool with 10 optional parameters and no output schema, this is a notable transparency gap.

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 sentence that fronts the essential action and resource. It's efficient and readable, though "various filtering options" is somewhat weak filler. Still, it earns its place as a concise summary.

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 tool has 10 optional params, no annotations, and no output schema, so the description needs to compensate with behavioral context. It does not describe what the response contains, how filters combine, or any defaults. This is incomplete for a realistically complex tool.

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 100%, with each parameter already described in the input schema. The description's "various filtering options" adds no new semantic value, but the schema does the heavy lifting, so the baseline 3 is appropriate.

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?

"Fetches news articles from Tiingo" clearly states the action and resource, and distinguishes this tool from sibling tools that handle prices and fundamentals. The phrase "with various filtering options" is vague, so it doesn't earn a 5, but the core purpose is unambiguous.

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?

Usage is implied by the tool name and sibling context: use this when news articles are needed, not price or fundamental data. The description does not explicitly state when to choose this over alternatives or when not to use it, so it provides only implicit guidance.

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