Zerodha MCP Integration

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Place an order' implies a write/mutation operation, the description doesn't disclose critical behaviors: whether this executes real trades, requires authentication, has rate limits, returns order confirmation, or what happens on failure. For a financial trading tool with zero annotation coverage, this is a significant gap.

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 appropriately sized but not optimally structured. The opening sentence states the purpose, but the parameter documentation could be better integrated. While efficient, it lacks the front-loaded clarity about what this tool fundamentally does versus siblings. Every sentence earns its place, but the structure could better guide the agent.

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 complex financial trading tool with 8 parameters, no annotations, and no output schema, the description is incomplete. It documents parameters well but misses critical context: authentication requirements, return values, error conditions, rate limits, and differentiation from sibling tools. The agent lacks sufficient information to use this tool safely and effectively.

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 0% schema description coverage, the description must compensate - and it does effectively by providing clear parameter explanations with examples for 'tradingsymbol' and enumerations for 'exchange', 'transaction_type', 'product', and 'order_type'. It clarifies conditional usage of 'price' and 'trigger_price' based on order type. This adds substantial value beyond the bare 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 the action ('Place an order') and the target system ('on Zerodha'), which is a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'place_mf_order' or 'place_mf_sip' - all involve placing orders but for different asset classes. The purpose is clear but lacks sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives like 'place_mf_order' (for mutual funds) or 'place_mf_sip'. There's no mention of prerequisites (authentication, account status), typical use cases, or constraints. The agent must infer usage from parameter names alone.

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