search_forum

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

With no annotations provided, the description carries the full burden and excels by disclosing key behavioral traits: it explains the search functionality, pagination behavior (increment page parameter if more results exist), and the structure of the return object. It also details query operators and sort options, which are critical for effective tool use.

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 and front-loaded, starting with the core purpose, followed by detailed parameter explanations, return value description, and practical examples. Every sentence adds value, such as the operator examples and pagination note, with no redundant or unnecessary information.

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 (search with operators and pagination), no annotations, and the presence of an output schema, the description is highly complete. It covers purpose, usage, parameters, return values, and behavioral aspects like pagination, leaving no gaps for an AI agent to understand and invoke the tool correctly.

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 100% schema description coverage, the description adds significant value beyond the schema by providing detailed examples of query operators (e.g., 'in:title', '@username') and sort order options with practical use cases. It clarifies parameter interactions, such as how 'page' works with pagination, enhancing understanding beyond the basic schema definitions.

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 purpose with a specific verb ('Search') and resource ('USCardForum for topics and posts'), distinguishing it from sibling tools like 'get_hot_topics' or 'get_new_topics' which retrieve predefined lists rather than performing custom searches. It explicitly mentions what is being searched (topics and posts) and matches the tool name directly.

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 when to use this tool (searching with a query) and includes example queries that illustrate common use cases. However, it does not explicitly state when not to use it or name specific alternatives among sibling tools, such as using 'get_topic_info' for detailed topic information instead of search results.

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