list_sse_filings

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

No annotations are provided, so the description carries the full behavioral burden. It adds only that data comes 'directly from sse.com.cn'; it does not state that the operation is read-only, how results are ordered, whether pagination beyond 'limit' applies, or any rate/auth constraints for a live external source.

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 tight sentence with the resource front-loaded and zero filler. Appropriate size for the operation.

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?

An output schema exists so return values need not be explained, and params are fully described. However, with no annotations and no usage guidance, the description is thin for a tool sitting among many near-identical sibling filing listers.

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 the schema already documents year, limit, title, and ticker_or_name with examples. The description contributes no additional parameter meaning, making the baseline 3 appropriate.

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?

States a specific verb (List) and resource (a SSE-listed company's disclosures), which implicitly separates it from the many sibling list_*_filings tools (SZSE/BSE/CSRC/HK). It identifies the market and data source, but does not explicitly differentiate itself from get_sse_company or get_sse_section.

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 when-to-use, when-not, or alternative guidance. With siblings like list_szse_filings, get_sse_section, and get_company available, an agent gets no help choosing this tool over them beyond the 'SSE' in the name.

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