finstack-mcp

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

Discloses data source (AMFI database) and authentication requirements (no API key) which compensates for missing annotations. However, omits rate limits, caching behavior, or error handling details despite having zero annotation coverage.

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 Args and Examples sections; front-loaded purpose statement followed by operational details. No redundant text, though the Examples block is somewhat lengthy it serves an essential educational purpose given the parameter flexibility.

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?

Adequate for a simple lookup tool with existing output schema; covers input semantics thoroughly and hints at return values via examples. Lacks only advanced operational details like rate limiting or multi-match resolution behavior.

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 has 0% description coverage, but description excellently compensates by defining query parameter as accepting either fund names or numeric scheme codes with concrete examples. Fully documents the single parameter's semantics and expected formats.

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 the latest NAV' for 'Indian mutual fund' resource, clearly distinguishing from stock-focused siblings like nse_quote and bse_quote. Specifies domain (Indian) and asset class (mutual fund) effectively.

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 concrete examples showing query patterns (name vs code) but lacks explicit guidance on when to choose this over equity tools or alternatives. No mention of prerequisites, dependencies, or error conditions.

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