finstack-mcp

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

No annotations provided, so description carries full burden. Discloses volume limit ('up to 10'), timeliness ('recent'), and output fields ('title, publisher, and link'). Missing cache duration, rate limits, or error behavior for invalid symbols.

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?

Efficiently structured with single-sentence purpose, return value summary, Args block, and Examples block. No filler text; front-loaded with essential information. Examples demonstrate parameter usage without verbosity.

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?

Complete for a single-parameter retrieval tool. Explains input (optional ticker), output structure (10 articles with specific fields), and usage patterns. Sufficient to invoke correctly without additional documentation despite zero schema coverage.

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 (only 'title': 'Symbol', 'type': 'string'). Description fully compensates by explaining semantics ('Stock ticker'), optionality ('optional'), default behavior ('Leave empty for general market news'), and valid formats via examples ('AAPL', 'RELIANCE.NS').

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?

Specific verb 'Get' + resource 'market news' + scope 'for a stock or general market' clearly defines the tool's function. Distinguishes from siblings like stock_quote (prices) or company_profile (static data) by focusing specifically on news retrieval.

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 clear Args section explaining optional symbol parameter ('Leave empty for general market news') and concrete examples showing specific ticker, exchange-specific ticker, and empty invocation. Lacks explicit contrast with alternative information tools (e.g., 'use this instead of sec_filing for news content').

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