list_disclosures_by_stock

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

No annotations present, so description carries full burden. It explains the return value (receipt numbers) and parameter constraints (lookback_years range 1-5). Does not mention output size or ordering, but output schema may address that. No contradictions.

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?

Short, direct, well-structured with separate lines for each parameter. Every sentence serves a purpose. No extraneous text.

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?

Adequate but incomplete: covers purpose and two of three parameters. Missing documentation for lookback_days. Could also mention that the output is a list of receipt numbers (implicit but not explicit). Output schema may compensate, but description should stand alone.

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 coverage is 0%, so description must compensate. It adds meaning for stock_code (example) and lookback_years (default, range). However, it omits the lookback_days parameter entirely, leaving it undocumented.

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?

Clearly states the action: list disclosure receipt numbers by stock code. Differentiates from siblings by specifying that the returned receipt numbers can be used with tools like get_disclosure_document, view_disclosure, and check_disclosure_risk.

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?

Provides context on when to use: to get receipt numbers for recent disclosures. Suggests subsequent usage with other tools. Does not explicitly exclude alternatives or state when not to use, but is helpful overall.

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