stock_sse_summary

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

The annotations already declare the read-only, idempotent, and non-destructive nature. The description adds the return type (pandas.DataFrame) and a URL to the source data but includes no additional behavioral details such as update frequency or data freshness. This is acceptable but minimal for a read-only tool.

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 extremely short and front-loaded with the name, but it repeats the same phrase '上海证券交易所-总貌' in the title and the return docstring. The URL is useful and there is no wasted prose, but the repetition is slightly redundant.

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 tool's simplicity (no params, no output schema), the description covers the essential information: what it returns and from where. It could mention the DataFrame columns or how current the data is, but for a zero-parameter summary endpoint, it is reasonably complete.

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 and the schema is an empty object, so the description is not expected to elaborate on parameters. The baseline of 4 applies because there is nothing to add beyond the schema.

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 names the resource: '上海证券交易所-总貌' (Shanghai Stock Exchange Overview) and provides the source URL, distinguishing it from sibling tools like stock_szse_summary. However, it lacks an explicit verb such as 'fetch' or 'get', so it reads as a noun phrase rather than a command.

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. There is no mention of scenarios, prerequisites, or exclusions, leaving an agent without the information needed to choose between this and related SSE/SZSE summary tools.

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