getFinancialStatementSymbols

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds only that coverage spans major global exchanges; it does not say whether the list is paginated, how current it is, roughly how many entries it contains, or what fields come back — and the trailing clause implies financial statements themselves are returned, which sets a wrong expectation about behavior.

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 opening clause is front-loaded correctly, but the second sentence is a run-on that ends in a grammatically broken dangling clause ("...are provided") and repeats value propositions already implied. The result is longer than needed while conveying less, and the confusing half undercuts the clear half.

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 zero-parameter list tool with no output schema, the description should at minimum say what each returned entry contains (symbol, company name, exchange, etc.). It gestures at coverage and content but never states the return shape, leaving a genuine gap even for a simple tool.

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 tool takes zero parameters and the schema is trivially empty at 100% coverage, so there is nothing for the description to disambiguate. The baseline for a zero-parameter tool applies.

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 first sentence states a specific resource (companies with available financial statements) and names the upstream API, but the second sentence blurs the purpose by saying the tool will "obtain up-to-date financial data including income statements, balance sheets, and cash flow statements," which describes what the returned symbols give access to, not what this tool returns. There is also no differentiation from close siblings such as getCompanySymbols, getSymbolChanges, or getCIKList, all of which also return symbol inventories.

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?

There is no statement of when to use this tool rather than getCompanySymbols, getActivelyTradingList, or getCIKList, and no prerequisites or exclusions are given. The only contextual hint is "companies listed on major global exchanges," which is scope, not usage guidance.

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