get_hk_section

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. 'Extract' implies a read-only operation, but it does not explicitly state non-destructiveness, permission requirements, rate limits, or error behavior when a PDF or section is unavailable. It adds only the source type (HK stock annual report PDF).

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, front-loaded sentence with no wasted words. The verb, resource, and domain are communicated immediately.

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. However, given the large set of similar section-extraction and HK-related sibling tools, the description lacks enough routing context to confidently choose this tool over alternatives. It is minimally adequate for a simple extraction tool but incomplete for selection among close siblings.

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 all three parameters. The description adds little beyond the schema: 'named section' aligns with the section parameter, and 'HK stock annual report PDF' contextualizes ticker_or_name and year, but no format or syntax details are added.

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 (Extract), resource (named section), and domain (HK stock annual report PDF). It is clearly about extracting report sections, though it does not explicitly differentiate itself from generic siblings like get_section, get_szse_section, or get_hk_financials.

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 guidance or alternatives are provided. The description does not explain when to prefer this tool over get_hk_financials, list_hk_filings, get_section, or other exchange-specific section tools. Usage is only implied by the HK annual report context.

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