get_fins_summary

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

Annotations already show this is a read-only, idempotent, non-destructive tool. The description adds useful context: Free plan data is delayed by 12 weeks, acceptable date formats, and FiscalPeriod label values. No contradictions with annotations.

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 relatively concise and well-structured, starting with a clear directive and listing return types. Minor redundancy in listing metrics twice, but overall efficient.

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 presence of an output schema (not shown), the description need not detail return values. It covers usage context, parameter constraints, and plan limitations, making it complete for a summary 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?

With 0% schema description coverage, the description effectively explains parameters: 'code' expects 5 digits (4-digit for ordinary shares) and 'date' expects YYYYMMDD or YYYY-MM-DD. This adds significant meaning beyond the bare schema.

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's purpose: 'Use this first for any financial metric query', enumerates specific metrics (EPS, BPS, revenue, profit, dividends, earnings forecasts), and specifies it returns quarterly financials. This distinguishes it from siblings like get_fins_details and get_fins_dividend.

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 description advises using this tool first for financial queries and notes that either code or date must be specified. However, it does not explicitly mention when to use alternatives like get_fins_details for more granular data, leaving the guidance incomplete.

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