market_depth

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

Discloses that it returns top 5 bid/ask prices and quantities, total queue size, and is real-time. No annotations exist, so description carries the burden; it covers essential traits without mentioning failure modes.

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?

Front-loaded with key purpose, then context, then parameter explanation, and example. Every sentence adds value; structure is logical and efficient.

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 no output schema visible, the description explains the output structure (top 5 buy/sell orders, total queue size). Covers setup, source, and parameter. Output schema exists for further detail, making this complete.

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?

Schema has 0% description coverage, but the description details the single parameter 'symbol' with examples and format (NSE symbol). Adds significant meaning beyond the schema's bare 'Symbol' title.

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 'Level 2 order book depth — top 5 bid/ask prices and quantities', specifying the verb and resource. It distinguishes from sibling tools like live_quote by emphasizing Level 2 depth.

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?

Provides context on source (exchange-licensed), cost (Zerodha/Angel One), and setup (API credentials). It does not explicitly list when not to use or alternatives, but the detail is sufficient for typical use.

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