block_deal_session

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it discloses nothing. It does not state whether the tool is read-only, what data it returns (e.g., deal records, timestamps, prices), or any limitations. For an agent considering invoking this tool, the behavior is entirely opaque.

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 short, but this is under-specification rather than effective conciseness. A single fragment 'NSE block deal session data' does not provide enough structure or information to be useful. It does not earn its place because it conveys no actionable content beyond the tool name.

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 tool has no parameters and no output schema, the description is the only source of context. It fails to explain what 'block deal session data' means, whether it is historical or real-time, or what the returned structure looks like. An agent cannot determine if this tool suits its task based on the description alone.

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 has zero parameters, so the baseline score is 4. The description adds no parameter-specific meaning, but none is needed because the input schema is empty. There is nothing about parameters that an agent needs to understand for this tool.

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 'NSE block deal session data' is a noun phrase that merely restates the tool name with 'NSE' prefixed. It lacks a verb indicating the action (e.g., retrieves, lists), making it essentially a tautology. It provides no differentiation from sibling tools like stock_quote or market_turnover.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention any use case, prerequisites, or context in which block deal session data would be relevant. There is no mention of alternatives or exclusions.

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