finstack-mcp

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

No annotations provided, so description carries full burden. Discloses specific return values including status enum states (OPEN, CLOSED, PRE_OPEN, POST_CLOSE), trading hours, and IST timezone. Uses 'Check' implying read-only behavior. Could improve by mentioning rate limits or real-time vs delayed data status.

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?

Perfectly structured with purpose first, followed by return values specification, arguments note, and usage example. Every sentence delivers distinct information without redundancy.

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?

Fully complete for a simple status tool. Despite context signals indicating an output schema exists, the description helpfully enumerates possible status enum values upfront. Covers all necessary aspects: purpose, return structure, and invocation pattern.

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?

Zero parameters with 100% schema coverage. Description explicitly confirms 'No arguments needed', which validates the empty schema structure and prevents confusion about missing parameters.

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?

Description explicitly states the action (check if open/closed) and specific resource (Indian stock market NSE/BSE). Clearly distinguishes from sibling data-fetching tools like nse_quote or stock_historical which handle price data rather than market operating hours.

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 example usage ('Shows if market is open right now') and explicitly notes 'No arguments needed'. Lacks explicit 'when not to use' guidance, but the unique purpose (market hours vs data retrieval) makes inappropriate usage unlikely.

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