finstack-mcp

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

With no annotations provided, the description carries the full burden and successfully discloses the return payload structure (constituents, prices, market cap, top 5 gainers/losers). However, it omits safety characteristics (read-only status) and operational constraints like rate limits or data freshness.

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?

The description is well-structured with clear 'Args' and 'Examples' sections. Every sentence provides value—purpose, return value, parameter specification, and usage examples—without redundancy or filler.

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 simplicity (1 parameter, no nested objects) and the existence of an output schema, the description is adequately complete. It helpfully summarizes the output schema contents and fully documents the single parameter, though it could explicitly confirm the read-only nature of the operation.

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?

The schema has 0% description coverage for the `index_name` parameter. The description fully compensates by specifying the valid enum values ('nifty50', 'sensex'), identifying the default ('nifty50'), and providing concrete usage examples.

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 it retrieves constituent stocks for Nifty 50 or Sensex with live prices, using specific verbs and resources. It distinguishes from siblings like `stock_quote` (individual stocks) and `nifty_index` (likely index value), though the tool name confusingly suggests only Sensex while the description clarifies dual support.

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?

The description provides clear examples showing valid inputs ('nifty50' vs 'sensex'), but lacks explicit when-to-use guidance comparing it to siblings like `nifty_index` or `stock_quote`. No prerequisites or exclusions are mentioned.

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