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 but offers minimal behavioral insight. It states 'modify' implies mutation but doesn't disclose permissions needed, whether changes are reversible, rate limits, error conditions, or what happens to unspecified fields. For a 6-parameter mutation tool, this is inadequate.

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 well-structured with a clear purpose statement followed by an 'Args:' section. Each parameter explanation is concise. However, the formatting with quotes and line breaks could be cleaner, and the purpose statement could be more front-loaded with critical context.

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 mutation tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It lacks information about what the tool returns, error handling, side effects, authentication requirements, and how partial updates work (null handling). The parameter explanations help but don't compensate for these gaps.

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 provides clear semantic meaning for all 6 parameters beyond their names, explaining what each controls (e.g., 'New amount per instalment', 'New frequency (weekly, monthly, or quarterly)'). This adds significant value over 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 tool's purpose: 'Modify a mutual fund SIP' with a specific verb ('modify') and resource ('mutual fund SIP'). It distinguishes from siblings like 'cancel_mf_sip' (termination) and 'place_mf_sip' (creation), but doesn't explicitly contrast them.

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 on when to use this tool versus alternatives like 'cancel_mf_sip' or 'place_mf_sip'. The description implies usage for updating existing SIPs but doesn't specify prerequisites, constraints, or appropriate contexts beyond the basic function.

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