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

Discloses behavioral details beyond annotations: it reads relevant parts of articles, returns passages, and mentions that subscriber-only articles from the past year provide summaries instead of full text. This transparency aligns with the readOnlyHint annotation and adds useful context.

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 moderately long but every sentence serves a purpose: it states the action, the output, the scenarios, and a query tip. It is well-structured and avoids fluff, making it appropriately sized for the information conveyed.

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, the description covers all essential aspects: what it does, when to use it (specific regions/topics), how it differs from alternatives, and a special caveat about subscriber-only content. Combined with the schema's parameter details, it is comprehensive.

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?

While the schema already documents each parameter, the description adds a valuable instruction: 'Wrap words in double quotes for an exact phrase.' This enriches the query parameter meaning without redundancy. Since schema coverage is 100%, the baseline is high, and the added tip elevates it.

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 function: searching the Trend archive and reading relevant parts of results. It also distinguishes it from sibling tools by explicitly saying to prefer it over a two-step search-and-read approach.

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?

Provides explicit guidance on when to use this tool: for any question about specific regions/topics (Azerbaijan, South Caucasus, etc.) and mentions to prefer it over calling search then reading articles individually. This 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.