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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds behavior beyond them: the default open-deadline filter and the exact set of fields returned (title, tendering unit, amount in 万元, deadline, sector, detail link). That return-shape disclosure matters because no output schema exists. It stops short of stating pagination limits or result caps in prose.

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?

Three short sentences, front-loaded with purpose, then the default filter, then the return fields, with no redundant or filler wording. Every sentence carries information the agent needs before calling it.

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 12 optional parameters, no required fields and no output schema, the description covers the right essentials: the platform scope, the default deadline filter and the return fields. It is adequate for correct invocation. Minor gaps remain, such as how results are ordered when sort is omitted: the schema names a default, but pagination limits and result caps are not explained.

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 100%, so parameter meaning is already fully documented, including the dl enum values, the band ranges, and the sort options. The description adds essentially nothing beyond the schema: its note that results are limited to open notices by default merely restates the dl=open default. This is the expected baseline when the schema does the heavy lifting.

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 a specific verb and resource: it searches tender notices (招标公告) across the national public-resource trading platform, scoped to engineering construction and government procurement. That is clear enough to separate it from get_notice, the sibling that fetches a single notice. However, the description never names that sibling or market_stats, so the separation is left to inference rather than stated explicitly.

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?

It gives one useful usage signal: by default it returns only notices that are still open for registration (未截止). That tells an agent the default behavior, but it offers no explicit when-to-use or when-not-to-use guidance and no comparison with the sibling tools (buyer_profile, get_notice, market_stats, win_probability).

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