show_financials

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

With no annotations, the description carries full burden but only states it fetches and returns 'key metrics' without detailing data freshness, rate limits, authentication, or any behavioral quirks. The term 'key metrics' is ambiguous and insufficiently transparent.

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 concise sentences with no wasted words. Front-loaded with verb and resource, making it efficient for an agent to parse.

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?

Given the tool returns multiple financial statements, the description should mention the output format, possible metrics, or any constraints. It only says 'key metrics' which is insufficient for an agent to understand what data to expect. No output schema exacerbates this gap.

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 67% (2 of 3 parameters described). The tool description does not add meaning beyond the schema, especially failing to explain the 'freq' parameter's values or the 'limit' parameter's period reference. The description should compensate for missing schema detail but does not.

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 the tool fetches SEC-reported financials for a ticker and specifies the types of metrics returned (income statement, cash flow, balance sheet). It distinguishes from sibling tools like show_balance or show_flow by implying it returns a comprehensive set of metrics.

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 guidance is provided on when to use this tool versus alternatives such as show_balance or show_flow. The description does not mention scenarios where users should avoid this tool in favor of more specific ones.

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