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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuine value beyond them by disclosing what the profile returns (counts of open vs total, sum/average amounts, agency and industry distributions, latest notices) — effectively substituting for the missing output schema. It does not mention response size, pagination, or behavior when the organization name is ambiguous or not found.

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?

A single dense sentence front-loads the profile contents (the reason to call the tool) and reserves the trailing parenthetical for the only invocation caveat. It is efficient, though the name-sourcing clause duplicates the schema description and could have been trimmed to avoid redundancy.

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 one required parameter, full schema coverage, and no output schema, the description carries the burden of explaining what comes back — and it does so by listing every reported dimension plus a 'recent notices' section. Combined with the read-only annotations and the name-sourcing hint, an agent has everything needed to invoke it correctly and interpret the result.

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?

There is a single parameter with 100% schema description coverage, so the schema already states it is the full organization name taken from the notice's 招标单位 field. The description's note about full names and sourcing from search_notices largely restates the schema, adding only a minor operational hint. Baseline 3 is appropriate 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 names a specific resource (招标单位画像 / a buyer organization profile) and enumerates exactly what it aggregates: total notices published, currently open registrations, total and average amount, frequently used agencies, industries, and recent notices. That enumeration makes the tool's scope clearly different from search_notices (searches notices) and market_stats (market-wide aggregates), so an agent can select it without opening the schema.

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 concrete usage context: this is a per-organization profile, and the parenthetical tells the agent how to obtain the required name ('可以从 search_notices 结果里拿'), which is a real prerequisite hint. What's missing is an explicit exclusion — e.g. when to prefer market_stats for aggregate industry data vs this per-buyer view — so the agent must infer the boundary.

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