bid_bigdata_bidding_info

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

No annotations provided. Description does not disclose behavioral traits such as pagination behavior, authentication needs, result limits, or data freshness. The agent is left guessing about side effects or constraints.

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?

Description is extremely concise (one short sentence). While not verbose, it lacks necessary detail for a tool with multiple parameters. Conciseness is positive but here it under-specifies.

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 no annotations, no output schema, and 0% parameter documentation, the description is wholly incomplete. Missing details on return format, error handling, 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?

Schema description coverage is 0%. Description does not explain the meaning or usage of any parameter, not even the required 'matchKeyword' or optional 'keywordType'. The agent must infer parameter semantics solely from names.

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?

Description states clearly that the tool queries bidding information enterprises participate in. It uses specific verb '查询' (query) and resource '招投标信息' (bidding info). While siblings exist, the description distinguishes it sufficiently from stats-oriented tools.

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 vs siblings like 'bid_bigdata_bid_search' or 'bid_bigdata_planned_projects'. The description provides no context for selection.

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