get_full_financial_statement

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

With no annotations, the description carries the behavioral burden itself. It states that the tool uses an external Open DART endpoint, returns every line item across the balance sheet, income statement, and other statements, and is scoped to a single business year and report type. It does not cover auth or rate limits, but for a read-only financial-data fetch the core behavior is clear.

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-oaded with the core purpose and uses a compact Args block. The phrase 'every line item' appears twice and the endpoint name adds mild redundancy, but it stays under roughly 130 words and contains no filler.

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 4-parameter external-data tool with no schema descriptions and no annotations, this description is largely complete: it covers every parameter, defaults, examples, allowed values, and the nature of the response. The only notable gap is explicit routing guidance between this and the sibling get_financial_statements.

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 input schea has no descriptions (0% coverage), but the description fully compensates: it defines corp_code with an example, year format, all four allowed report_type values, and both fs_div values with their defaults. This is exactly the semantic content the schema lacks.

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 opens with a specific verb and object: 'Get the complete financial statement (every line item) for one period.' It further identifies the Open DART full-statement endpoint and explicitly enumerates which statements it covers, making it distinguishable from the tersely named sibling get_financial_statements.

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 wording 'complete' and 'every line item' implies this is the tool for full financial-statement detail, but it never names alternatives or gives an explicit when-to-use/when-not-to-use rule. No mention of get_financial_statements as the lighter or summary alternative, so the agent must infer the boundary.

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