finstack-mcp

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

No annotations are provided, so the description carries the full burden. It discloses the scope (Nifty 50 components, top 10 limit) and temporal context ('today'), but omits behavioral details like data refresh frequency, market hours requirements, or whether the results are cached.

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 sections: summary, return value description, Args, and Examples. Information is front-loaded and every section adds value. Slightly verbose format (using 'Args:' and 'Examples:' headers) but appropriate given the lack of schema metadata.

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 single-parameter tool. The existence of an output schema reduces the need for detailed return value description in the text. The description successfully compensates for the zero schema coverage by documenting the parameter options inline.

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 compensates effectively via the 'Args' section, documenting the three valid options for `mover_type` (gainers, losers, active) and their semantic meanings. Minor gap: it does not mention the default value 'gainers' specified in the 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?

Clearly states it retrieves 'today's top performing stocks on NSE' and specifies it returns 'top 10 stocks by the specified criteria from Nifty 50 components.' However, it does not explicitly differentiate from sibling tools like `nse_quote` (specific stock) or `stock_screener` (custom filters).

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 how to invoke the tool with each mover_type option. However, it lacks explicit guidance on when to use this tool versus alternatives like `nse_52week_scanner` or `sector_performance`, leaving the agent to infer based on the 'top 10' constraint.

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