find_similar_news

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

With no annotations, the description fully carries the burden. It explains threshold strictness, limit actual vs. requested, include_url for token saving, and a display strategy. This gives comprehensive behavioral insight.

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 but includes a data display strategy section that, while useful, adds length. It is mostly front-loaded and efficient, though slightly verbose.

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 parameter count, lack of schema descriptions, and no annotations, the description is highly complete. It covers all parameters, behavior, and output expectation, and there is an output schema to cover return structure.

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?

Despite 0% schema description coverage, the description thoroughly explains each parameter: reference_title (the title), threshold (similarity threshold with note), limit (max 100, actual may be less), include_url (default false for token saving). It adds meaning beyond schema.

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's action: finding similar news based on a specified title. It distinguishes itself from sibling tools like search_news by focusing on similarity rather than general search.

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 clear context for use (when needing similar news) and includes practical notes (e.g., threshold impact, limit behavior). However, it lacks explicit guidance on when not to use or direct comparison with alternatives.

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