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. It discloses key behavioral traits: it opens a browser (implying user interaction) and starts a local server (implying network activity). However, it lacks details on error handling, timeouts, or what happens after the redirect, leaving gaps for a tool with potential complexity.

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 two concise sentences that directly explain the tool's purpose and mechanism without any fluff. It is front-loaded with the main action and efficiently communicates the necessary steps.

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 annotations, no output schema, and 0 parameters, the description is minimal but covers the core action. However, for a login flow tool that likely involves user interaction and network operations, it lacks details on expected outcomes, error cases, or integration with sibling tools like 'check_and_authenticate', making it somewhat incomplete.

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 tool has 0 parameters, and schema description coverage is 100% (as there are no parameters to describe). The description does not need to add parameter semantics, so a baseline of 4 is appropriate, as it efficiently avoids unnecessary details.

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 specific action ('Start the Zerodha login flow') and the mechanism ('by opening the login URL in a browser and starting a local server to handle the redirect'). It distinguishes itself from sibling tools like 'check_and_authenticate' by focusing on initiation rather than verification or other authentication steps.

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 implies usage at the beginning of a login process, but does not explicitly state when to use this tool versus alternatives like 'check_and_authenticate' or 'get_request_token'. It provides some context (starting the flow) but lacks explicit guidance on prerequisites or exclusions.

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