stock_szse_sector_summary

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the source URL and parameter choices ('当月'/'当年'), which provides context beyond annotations, but does not mention edge cases or error behavior.

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 compact and front-loaded with the Chinese title and URL. It efficiently lists parameters and return type without unnecessary verbosity. The docstring-style structure is clear and every line contributes useful information.

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?

The description provides the source URL, parameter meanings, and return type (pandas DataFrame), which is adequate for a simple read-only tool. However, it does not describe the columns or structure of the returned data, and with no output schema, a bit more detail on the expected data shape would improve completeness.

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 schema has no descriptions (0% coverage), but the description meaningfully explains both parameters: symbol is a choice of {'当月', '当年'} and date is 交易年月 (trading year-month, with default '202501' illustrating format). This compensates for the missing schema descriptions, though the exact date format is implicit.

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 retrieves Shenzhen Stock Exchange stock industry trading data (股票行业成交数据), with the title confirming it's a sector summary. It distinguishes from siblings by specifying SZSE and sector-level data, though it lacks an explicit verb like 'get' or 'fetch'.

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 alternatives. It does not mention exclusions or recommend sibling tools for related needs, leaving the agent to infer from the name and title alone.

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