free_it_search

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

No annotations exist. The description does not disclose behavioral traits such as rate limits, authentication needs, or how results are structured (pagination, filtering). The return value is vaguely described as 'Text content with the IT search results.'

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 a list of parameters with brief Chinese descriptions, which is somewhat structured. However, it repeats the parameter list pattern and could be more compact. Every sentence adds some value but lacks conciseness.

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, no annotations, and an output schema not described, the description is incomplete. It fails to explain result format, pagination, error handling, or any usage constraints beyond basic parameter fields.

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 coverage is 0%, so description must compensate. However, parameter descriptions are incomplete and contain contradictions: language default is 'auto' in schema but '中文' in description; safe_search is string in schema but described as int. This misleads the agent.

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 states '信息技术搜索' meaning IT search, and lists parameters typical for a search tool. It distinguishes itself from siblings like free_general_search by focusing on IT topics, but lacks explicit detail on what IT domain covers.

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?

No guidance on when to use this tool versus other search siblings. There is no comparison or context about scenarios suited for IT search vs general or specialized searches.

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