get_key_ratios

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

With no annotations, the description carries the full burden. It only lists ratios but does not disclose data source, update frequency, or limitations (e.g., whether all ratios are always available). This is insufficient for a data retrieval tool.

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 sentences with no fluff: one listing the ratios, one providing an example. Every sentence adds value, and the structure is front-loaded.

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 tool without output schema, the description covers the return content (list of ratios) but misses context like data scope (latest vs. historical) and any prerequisites (e.g., valid symbol). It is minimally adequate.

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 schema has 0% description coverage, but the example 'get_key_ratios("RELIANCE")' adds meaning, indicating symbol is a stock ticker. However, it does not specify format (e.g., NSE/BSE suffix) or case sensitivity, leaving some ambiguity.

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 key financial ratios and lists specific ratios (PE, PB, etc.), identifying the resource and action. However, it does not explicitly distinguish from sibling tools like get_company_profile or get_income_statement that might also provide some ratios.

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 on when to use this tool versus alternatives. The description does not mention when this is appropriate (e.g., for fundamental analysis) or when to prefer other tools like get_balance_sheet.

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