realtime_forums_search

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

No annotations are provided, and the description only states that it performs a search. It does not disclose the return format, any side effects, rate limits, or authentication requirements, leaving a significant behavioral gap beyond the obvious read-only nature.

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 succinct and front-loaded with its purpose, followed by a clear operations list. Every sentence serves a purpose with no wasted words.

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?

Without annotations or an output schema, the description should explain what the tool returns and any limitations. It only provides minimal operational detail (operation and query), leaving the agent uncertain about response format and usage constraints.

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 input schema only describes an operation enum and a generic args object. The description adds the required parameter name 'query' for the search operation, which is meaningful beyond the schema. However, it does not elaborate on the query's format or any optional parameters.

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 searches discussion forums and community threads (Reddit and similar) for a query. This specific verb and resource distinguishes it from sibling search tools like realtime_news_search or realtime_video_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 implies usage for forum searches but provides no explicit guidance on when to use this tool over alternatives, nor any exclusions. No alternative tools are mentioned, so the usage context is implied rather than stated.

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