get_disclosure

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

No annotations exist, but the description fully details behavioral traits: returns TOC for large docs, section queries, and sub-TOC for large sections, with 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?

The description is front-loaded with the main action and includes essential procedural guidance, though slightly verbose with repeated navigation instructions.

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?

Covers return types, large document handling, and section queries comprehensively, but lacks output schema details like field names beyond the TOC example.

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?

Despite 0% schema coverage, the description thoroughly explains 'rcept_no' (14-digit from get_disclosure_list) and 'section_id' (from TOC sections[].id), including default behavior, adding critical meaning beyond the schema.

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 'fetches parsed disclosure documents' and references 'get_disclosure_list' for the rcept_no, distinguishing it from sibling tools like listing or info tools.

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 expect TOC versus full content, how to query sections, and provides a workflow for handling large documents, including notifying the user about remaining sections.

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