Zerodha MCP Integration

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. It states the action ('Place') but doesn't mention whether this is a read-only or destructive operation, what permissions are required, potential costs, rate limits, or what happens on success/failure. For a financial transaction tool, 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 front-loaded with the purpose in the first sentence, followed by a structured list of parameters with brief explanations. It's efficient with minimal waste, though the formatting as a bullet-like list in the 'Args:' section could be slightly more polished.

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 of a financial SIP placement tool with 7 parameters, no annotations, and no output schema, the description is moderately complete. It covers parameter semantics well but lacks behavioral context, usage guidelines, and output details, leaving gaps for an AI agent to invoke it correctly in real-world scenarios.

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 description adds substantial meaning beyond the schema, which has 0% description coverage. It explains each parameter's purpose (e.g., 'tradingsymbol' with an example, 'instalments' with a minimum, 'frequency' with options, and optional parameters with context). This compensates well for the schema's lack of descriptions, though it doesn't cover all nuances like format constraints for 'tradingsymbol'.

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 a mutual fund SIP') and specifies it's a Systematic Investment Plan, which distinguishes it from one-time orders. However, it doesn't explicitly differentiate from 'place_mf_order' or 'modify_mf_sip' among the sibling tools, which would require a 5.

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 provided on when to use this tool versus alternatives like 'place_mf_order' for one-time investments or 'modify_mf_sip' for existing SIPs. The description lacks context about prerequisites, such as authentication or account setup, which are implied by sibling tools like 'check_and_authenticate'.

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