Zerodha MCP Integration

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

No annotations are provided, so the description carries full burden. It only states the action ('place a mutual fund order') without disclosing behavioral traits such as whether this is a destructive/mutative operation, authentication requirements, rate limits, order execution timing, confirmation mechanisms, or error handling. For a financial transaction tool with zero annotation coverage, this is a critical 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 and front-loaded: the first sentence states the purpose, followed by a structured 'Args:' section. Each line is brief and relevant, with no wasted words. However, the formatting could be slightly improved for readability (e.g., bullet points instead of plain text).

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 complexity (financial transaction tool), lack of annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't cover behavioral aspects, return values, error cases, or contextual dependencies like market hours or balance requirements. For a tool that places orders, this leaves the agent with insufficient information to use it 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?

Schema description coverage is 0%, so the description must compensate. It lists parameters (tradingsymbol, transaction_type, amount, tag) with brief examples (e.g., 'BUY or SELL'), adding some meaning beyond the bare schema. However, it doesn't explain parameter formats (e.g., amount units, tag purpose), constraints, or dependencies, leaving significant gaps given the 4 parameters.

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 tool's purpose: 'Place a mutual fund order' with specific parameters like trading symbol, transaction type, and amount. It distinguishes from some siblings (e.g., 'place_mf_sip' for SIP orders) but doesn't explicitly differentiate from 'place_order' (which might be for stocks/ETFs). The verb 'place' is specific, and 'mutual fund order' identifies the resource.

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. It doesn't mention when to choose 'place_mf_order' over 'place_mf_sip' (for SIPs) or 'place_order' (possibly for other securities), nor does it specify prerequisites like authentication or account setup. Usage is implied only by the tool name and parameters.

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