get_bankruptcy_report

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

No annotations are provided, and the description does not disclose behavioral traits such as idempotency, side effects, authentication requirements, or response characteristics. The description is minimal and fails to inform about the tool's safety or operational impact.

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: one sentence explaining the purpose, followed by a clear list of parameters with format hints. Every word adds value, and the structure is front-loaded.

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?

With no output schema and minimal description, the tool lacks critical context such as return value structure, pagination, error handling, or rate limits. For a data retrieval tool with 3 parameters, it is minimally adequate but leaves gaps in completeness.

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 meaning beyond the schema by specifying the format for corp_code (8-digit DART code) and the date format (YYYYMMDD) for bgn_de and end_de, along with optionality. This compensates for the 0% schema coverage.

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 explicitly states the tool retrieves key bankruptcy occurrence information from a major report. The name 'get_bankruptcy_report' aligns with the description, and it is distinct from sibling tools like 'get_rehabilitation_report'.

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 lists parameters but does not provide explicit guidance on when to use this tool versus alternatives (e.g., rehabilitation report). It implies usage for bankruptcy data but lacks 'when to use' or 'when not to use' context.

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