kite-mcp

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

Discloses important fallback behavior not present in annotations: 'Falls back to holdings/positions data if the market data API is not available.' This warns the agent that returned data may originate from cached portfolio data rather than live market feeds.

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?

Three sentences, each earning its place: purpose declaration, input format specification, and fallback behavior. Information is front-loaded and there is no redundant 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?

Appropriate for a read-only data retrieval tool. With annotations covering safety profile (readOnlyHint) and an output schema available, the description adequately covers the live data semantics, input formatting, and fallback caveats without needing to detail return structures.

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 carries full burden for parameter documentation. It successfully compensates by specifying the required NSE: prefix format and providing valid examples, clarifying what the 'instruments' array expects.

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?

States specific action 'Get live market quote' with clear scope 'one or more instruments'. The 'live' qualifier distinguishes from sibling get_historical_data, and 'quote' distinguishes from get_holdings/get_positions (portfolio data vs market data).

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?

Provides explicit parameter formatting guidance 'Use NSE: prefix for stocks' with concrete examples (NSE:RELIANCE). While it doesn't explicitly name alternative tools (like get_ohlc), the 'live' descriptor and examples provide clear usage context.

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