finstack-mcp

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

With no annotations provided, the description carries full disclosure burden and effectively documents return structure (current value, change %, day's high/low, 52-week range). However, it omits non-obvious behavioral traits like data freshness, caching, or rate limits.

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?

Well-structured with clear docstring sections (Args, Examples) that front-load critical information. The formatting is slightly verbose but every section earns its place by providing necessary context not present in the structured schema.

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 tool's low complexity (1 parameter, simple lookup), presence of output schema, and extensive parameter documentation, the description is complete. It adequately covers the tool's scope without requiring speculation about implementation details.

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 coverage is 0% (no descriptions in JSON schema), but the description fully compensates by exhaustively documenting the index_name parameter with all valid enum values (NIFTY50, SENSEX, BANKNIFTY, etc.) and their precise meanings, including aliases like 'NIFTY'.

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 'Get current value of Indian market indices' with specific verb and resource. It distinguishes from siblings like stock_quote or nse_quote by explicitly focusing on broad market indices (NIFTY50, SENSEX, BANKNIFTY) rather than individual securities.

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 implied usage guidance through examples showing specific index selection vs 'ALL', but lacks explicit when-to-use comparisons against siblings (e.g., when to use this vs stock_quote for individual stocks). No exclusion criteria or alternative tool recommendations are provided.

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