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

With no annotations provided, the description carries the full burden and does substantial work: it discloses the data source ('from each company's own filed results'), consolidation behavior ('Consolidated where the company files it'), freshness mechanism ('Every block carries its own date and age'), and units ('Values in INR crore'). It does not discuss auth, rate limits, or error behavior, but for a read-oriented data tool this is strong transparency.

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 dense and information-rich, but it is structured as one long run-on paragraph. Every element is relevant, yet breaking the content into bullets or shorter sentences would improve scannability. It is not overly verbose, but it is not optimally structured.

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?

The description is unusually complete for a tool with no output schema: it enumerates the exact metrics, periods, ratios, shareholding fields, units, and input requirement. The main gap is that the 'period' parameter is optional but no default behavior is stated, and the response shape is not described. Overall, an agent has enough context to call this tool correctly.

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 100%, so both parameters are already documented. The description adds only 'Pass an NSE trading symbol,' which largely repeats the schema. Baseline 3 is appropriate because the schema handles parameter semantics adequately.

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 identifies the resource: Indian listed-company fundamentals sourced from filed results, including P&L, balance sheet, ratios, and shareholding pattern. It is specific and unambiguous, though it does not explicitly differentiate this tool from potentially overlapping siblings like hsh-company-intelligence.

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 states the key invocation requirement: 'Pass an NSE trading symbol. Per call.' This gives clear how-to context but no explicit when-to-use guidance, alternatives, or exclusions relative to sibling tools. Usage is implied rather than fully specified.

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