get_disclosure

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

No annotations are provided, and the description only states it retrieves a list of recent disclosures. It discloses no behavioral traits such as read-only nature, error handling, pagination, or rate limits, which are important for safe invocation.

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 concise with no wasted words. The purpose is front-loaded in the first line, followed by usage context and parameter details. Every sentence is essential.

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?

For a simple lookup tool with one parameter and an output schema available, the description adequately covers the context. It explains the data source (DART) and type of information (recent disclosures). Missing details like date range or limitation to recent, but overall sufficient for selection.

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 description adds value beyond the input schema by specifying that the 'code' parameter requires a 6-digit stock code (e.g., '005930'), providing concrete formatting guidance. With 0% schema coverage, this compensates well for the single parameter.

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 it returns a list of recent disclosures for a stock from DART. It specifies the stock code parameter and provides example queries (disclosure, IR, etc.), making its purpose distinct from siblings like get_price or get_us_filings.

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?

The description explicitly mentions when to use the tool (questions about 'disclosure', 'IR', etc.) but does not exclude alternatives or provide when-not-to-use scenarios. Given sibling tools cover other domains, this is adequate.

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