nse_bulk_deals

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

The description discloses that it shows large transactions exceeding 0.5% of shares, but does not mention data freshness, delays, or other behavioral aspects. Given no annotations, it carries the full burden but only partially meets it.

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 extremely concise: four lines including an example. It front-loads the purpose and uses bullet-style formatting for clarity.

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 tool with no parameters and no annotations, the description covers the essential: what it does, the threshold, and an example. It is complete for its complexity level.

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?

With zero parameters, the baseline is 4. The description confirms 'No arguments needed' and provides an example call, which adds clarity beyond the empty schema.

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 recent bulk and block deals, specifying the threshold of 0.5% of total shares. This distinguishes it from other NSE tools that provide different data or timeframes.

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?

It explicitly states 'No arguments needed' and provides an example. It also mentions utility for tracking institutional activity. While it doesn't compare directly with siblings, the context is sufficient for a zero-argument tool.

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