Idx Get Keystats

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Fetch' clearly signals a read-only operation and 'official audited' adds a credibility cue, but there is no mention of data freshness, coverage limitations, or error behavior. These gaps are not covered elsewhere.

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 a single focused sentence that front-loads the action and resource, lists the key data categories, and names the source. There is no redundancy or filler.

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 single-parameter fetch tool with a fully documented input schema and an output schema, the description covers the essential context: what data is returned and from where. Minor omissions such as reporting frequency or units are unlikely to prevent correct invocation.

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 already provides 100% parameter coverage, including the ticker format and concrete examples like 'MYOR' and 'BBCA'. The description adds no additional parameter-level semantics beyond naming Stockbit as the source, so the baseline of 3 is appropriate.

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 uses a specific verb ('Fetch') and a clearly enumerated resource: official audited financial ratios, balance sheet, valuation, and Piotroski F-score from Stockbit. This distinguishes it from sibling tools like idx_get_market_quote (quotes) and idx_get_dividends (dividends), making its scope unambiguous.

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 implies usage for fundamental/valuation lookups by naming the exact data categories, but it does not explicitly state when to use this tool instead of siblings or mention any exclusion conditions. There is no reference to alternatives such as idx_sanitize_financials or idx_stockbit.

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