get_disclosure

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

No annotations provided, so description carries full burden. Discloses behavior: returns TOC for large docs, section_id retrieves subsections, and sub-TOC for very large sections. Lacks details on error handling or auth, but sufficient for the agent.

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?

Three sentences, well-structured with clear progression: purpose, behavior on large docs, then action steps. Front-loaded with main verb. Could be slightly tighter but very informative.

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 no output schema or annotations, description sufficiently covers key behaviors: large doc handling, section navigation, and user guidance. Lacks details on TOC format but enough for an agent to use correctly.

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 100%, so baseline is 3. Description adds significant meaning for section_id: explains its behavior (full doc vs TOC vs section retrieval). This goes beyond the schema description.

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 the tool 'parses and fetches original disclosure report files' via DART API, with specific verb and resource. It distinguishes itself from siblings like get_disclosure_list (list) and get_financial_statement (financial data).

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?

Explicitly describes when to use section_id for large documents (>1MB) and provides a complete workflow: get TOC, query sections, then inform user of remaining sections. This guides the agent on proper usage vs alternatives.

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