get_bulk_block_deals

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

With no annotations provided, the description carries the full burden. It only states the data content and time scope ('Today's'), but doesn't disclose behavior like pagination, limit handling, rate limits, or any side effects. The description is minimal and adds little beyond the obvious read operation.

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, concise sentence that front-loads the main purpose. It is efficient and easy to read, though it could be slightly more structured with a clear breakdown of included deal types.

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 tool has one parameter that is not explained, no output schema, and no annotations. The description provides the data scope but leaves the agent without knowledge of how the limit parameter affects results or any output format expectations. This is inadequate for a tool that should be easily callable.

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 only parameter, 'limit', is completely undocumented in the description. Schema description coverage is 0%, so the agent has no hint about what limit controls (e.g., number of results returned). The description adds no value to parameter understanding.

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 a specific resource (bulk deals, block deals, short-selling disclosures on NSE) and the information returned (who bought/sold what at what price). It is distinct from siblings like get_market_pulse or get_top_movers by naming a specialized data type.

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 today's bulk/block deals on NSE, but provides no explicit when-to-use vs alternatives or exclusions. An agent can infer the use case from the resource type, but there is no guidance on when not to use it or how it differs from other market data tools.

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