行业估值水平

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

No annotations are present, so the description carries full responsibility for disclosing behavioral traits. It only states the action ('获取' - get) and the data elements (P/E, P/B), but does not mention data source, update frequency, scope limitations, or any other behavioral characteristics. The verb implies a read operation, but that is not explicit.

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, concise sentence that conveys the essential information without wasted words. It is front-loaded with the action and resource, making it easy to parse.

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?

For a simple, zero-parameter tool without an output schema, the description adequately communicates what the tool returns: an overview of Shenwan L1 industry valuations with P/E and P/B. It is complete enough for an agent to select and invoke the tool correctly, though it could benefit from mentioning the format or granularity of the overview.

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 tool has zero parameters, so the schema coverage is 100% and the baseline is 4. The description does not need to explain parameter semantics, and it adds meaningful context by specifying the exact metrics (P/E, P/B) the tool retrieves.

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 the tool's function with a specific verb ('获取' - get) and resource ('申万一级行业估值' - Shenwan L1 industry valuation), explicitly mentioning the metrics (P/E, P/B). This distinguishes it from siblings like sector_rotation or stock_sector_fund_flow_rank.

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?

The description implies that this tool is for obtaining an industry valuation overview, but it does not explicitly state when to use it versus alternatives or any exclusions. No usage guidance is provided beyond the basic purpose.

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