bid_bigdata_bid_search

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

No annotations are provided, and the description lacks any behavioral information (e.g., read-only nature, rate limits, side effects). It only describes parameters, leaving the agent uninformed about tool behavior.

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 concise with a clear front-loaded purpose sentence followed by a parameter list. It could be improved with structured formatting (e.g., markdown) but is efficient.

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?

With 11 parameters, no schema descriptions, no output schema, and no annotations, the description should provide more context (e.g., output format, examples, pagination details). It covers parameters partially but lacks completeness.

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 description lists several parameters with brief explanations (e.g., matchKeyword, biddingType, pageSize max), adding value beyond the schema which lacks descriptions. However, it omits three parameters (biddingPurchasingType, biddingProjectMinAmount, biddingProjectMaxAmount) and provides no examples.

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 it is for querying and filtering bidding announcement information ('查询和筛选招投标公告信息'), and the tool name 'bid_search' aligns. It implicitly distinguishes from siblings like statistics and detail tools, but does not explicitly differentiate.

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 alternatives, such as other bid_bigdata tools or unrelated search tools. Missing context on prerequisites or exclusions.

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