financial_balance_sheet

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only says 'get balance sheet data' without disclosing what the response contains (line items like assets, liabilities, equity), whether prior or trailing periods are included, or if there are limits on requested periods. For a data-retrieval tool with no annotation safety profile, this is minimal transparency.

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?

Single sentence, zero waste - efficient and to the point. However, the extreme brevity borders on under-specification given the clarity gaps in purpose and usage. It earns points for compactness but doesn't over-earn because the brevity sacrifices informational value.

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?

There is an output schema present, which helps complete the picture of return values. However, given there are 20 sibling tools including other financial statement tools, the description should do more to differentiate this tool. The 3 parameters are each documented in the schema, and the output schema exists, but the description leaves gaps in when/how to use this tool relative to its financial siblings.

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 description coverage is 100%, so all 3 parameters (symbol, period, source) are documented in the schema. The description adds no parameter-level meaning beyond what the schema already provides. Baseline 3 is appropriate since the schema fully covers parameters and the description contributes no additional semantic context.

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 states 'Get balance sheet data for a company' - a clear verb+resource but very terse. It doesn't distinguish itself from sibling financial tools like financial_income_statement, financial_cash_flow, or financial_ratio beyond the name itself. The purpose is understandable but lacks scope clarity (historical range, entity framing) that would help a user pick it among siblings.

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?

No when-to-use or when-not-to-use guidance is provided. An agent cannot determine when to choose this over financial_income_statement, financial_cash_flow, or financial_ratio based on the description alone. There's no mention of alternatives, prerequisites, or context suggesting this is the right tool for balance-sheet-specific needs vs other financial statements.

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