find_related_news

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

With no annotations, the description carries full behavioral burden. It explains that results are sorted by similarity, that `include_url` saves tokens, and how the date range works. It does not mention potential limitations like data freshness or rate limits, but the core behavior is transparent.

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 well-structured with a one-line summary, Args section, Returns, and Examples. It is somewhat lengthy due to date_range details, but every part earns its place and the structure aids comprehension.

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 5 parameters and an output schema, the description covers functional semantics, parameter details, output format, and examples. It lacks edge cases or error handling, but it is sufficiently complete for an agent to use the tool correctly in most scenarios.

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 fully explains every parameter: `reference_title` (full/partial), `date_range` (with preset and custom formats), `threshold` (meaning and default), `limit`, and `include_url` (purpose and token-saving). This is exemplary parameter documentation.

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 finds news related to a specified title and supports current/historical data. It uses specific verbs and resources, but does not explicitly distinguish itself from siblings like `search_news` or `get_latest_news`.

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 detailed parameter usage, date range formats, and examples, making it clear how to invoke the tool. However, it does not explicitly state when to use this tool instead of alternatives such as `search_news`, nor does it list exclusions.

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