Get Company Financials

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

Annotations already mark it read-only and idempotent; the description adds valuable behavioral context: data source (SEC EDGAR XBRL), provenance of each figure (form and filing date), and the absence of third-party transformation. 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?

Two short sentences in the first paragraph list concrete data points; the second paragraph is a crisp usage directive. Every sentence serves a purpose with no redundancy.

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 simple single-parameter read-only tool, the description covers what data is returned (with field list), data source, and reliability context. No output schema exists, but the returned items are enumerated, making the tool self-sufficient.

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 has 100% coverage for the single parameter 'symbol' with a clear example. The description adds no additional parameter-level detail, so it remains at the baseline for high 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 clearly states it retrieves headline financials from SEC EDGAR XBRL filings, naming specific metrics (revenue, net income, EPS, etc.). It distinguishes itself from the sibling get_company_profile by emphasizing it uses the actual filing rather than a third-party summary.

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 advises to prefer this tool over get_company_profile when accuracy matters and provides the reason ('filing itself, not a third-party summary'). This is a clear when-to-use directive with an identified alternative.

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