brsr_esg

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

With no annotations, the description lists the types of data provided but lacks details on limitations (e.g., only top 1000 companies, data freshness), error handling, or authentication. It implicitly mentions the scope via SEBI mandate but does not disclose behavioral traits like rate limits or response format beyond what is listed.

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 front-loaded with the core purpose but includes several paragraphs of background (e.g., comparison to paid sources) that are informative but not essential for tool invocation. The list of disclosures adds redundancy. It could be trimmed to improve conciseness.

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 single parameter and existence of output schema, the description sufficiently covers what output to expect, including specific data types like filing links and disclosure categories. It is complete enough for a data retrieval tool, though it does not mention potential errors or empty results.

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 single parameter 'symbol' is described as NSE stock symbol with concrete examples (RELIANCE, TCS), adding meaning beyond the schema which only defines type string. This compensates well for the 0% schema description coverage, though it does not include constraints like uppercase or format.

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 provides BRSR ESG data for listed companies, including filing links and disclosures. While it does not explicitly start with a verb, the purpose is unambiguous and specific. It does not explicitly differentiate from siblings but is sufficiently distinct.

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 provides background on BRSR mandate and free availability but does not explicitly guide when to use this tool versus alternatives. No exclusions, prerequisites, or contextual usage tips are given, leaving the agent without clear selection criteria.

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