get_bse_intraday_data

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

With no annotations, the description carries the behavioral burden. 'Get' signals a read-only data retrieval and 'most-active-by-volume/value' clarifies the data selection/ordering behavior, but it does not disclose operational details such as data freshness, login requirements, or rate limits.

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, front-loaded sentence with no filler or repetition. Every word contributes to identifying the tool's purpose.

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 zero-parameter data-retrieval tool, the description names the exchange, the data category, and the selection criteria, and an output schema exists to document the return shape. It is slightly incomplete because it does not explicitly contrast with get_nse_intraday_data or state usage caveats, but the simple scope makes it sufficient for 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 tool accepts zero parameters and schema description coverage is 100%, so there is no parameter documentation burden on the description. Per the baseline for tools with no parameters, this is a 4.

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 and resource: 'Get BSE intraday most-active-by-volume/value data'. It clearly identifies the exchange (BSE) and the selection criteria (most active by volume/value), which distinguishes it from sibling tools such as get_nse_intraday_data and other market-data endpoints.

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 phrase 'BSE intraday' implies this tool is for BSE market data, so the usage context is evident by contrast with the NSE sibling. However, it does not explicitly state when to choose this tool over alternatives or describe any exclusions, leaving the routing decision to inference.

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