bid_bigdata_tender_stats

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

With no annotations provided, the description must disclose behavioral traits. It only states the tool's function but does not mention read-only nature, data freshness, rate limits, authentication requirements, or whether it returns aggregated counts or detailed records. This is insufficient for a tool with no annotation support.

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 single sentence that conveys the core purpose without extraneous words. It is front-loaded and efficient, though it could benefit from slight structure (e.g., listing parameters).

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 absence of annotations and output schema, the description should provide more context about the return format (e.g., count, summary fields), pagination, and scope. The tool has 2 parameters and sibling tools with varying functionality, so the minimal description leaves gaps for an agent to correctly invoke the tool.

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 adds partial meaning by indicating that matchKeyword can be an enterprise name or unified social credit code. However, it does not explain the keywordType parameter, and the schema has 0% description coverage. The description adds some value but leaves ambiguity about the optional parameter.

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 that the tool obtains statistical items of bidding information based on enterprise name or social credit code. This is clear and uses a specific verb+resource. However, it does not differentiate from siblings like bid_bigdata_bidding_info or bid_bigdata_bid_win_stats, which may cause confusion.

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 is provided on when to use this tool versus its siblings. There is no mention of prerequisites, when-not-to-use, or alternatives. The agent lacks context for selecting this tool over similar ones.

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