finstack-mcp

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

With no annotations provided, description carries full disclosure burden. It successfully reveals the richness of returned data (current rate, daily change, high/low, 52-week range) beyond a simple scalar value. Minor gap: doesn't specify if 'live' means real-time or delayed data, or mention rate limiting.

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 hierarchy: purpose → return values → parameters → examples. Front-loaded with the essential action in the first sentence. Five examples are numerous but necessary given the lack of schema enums or descriptions; no extraneous marketing language.

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 simple 2-parameter complexity and presence of output schema, the description is appropriately complete. It pre-emptively explains what the output contains (addressing the output schema), documents both parameters despite schema deficiencies, and provides sufficient context for an agent to invoke correctly.

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?

Excellent compensation for 0% schema description coverage. 'Args' section clearly defines from_currency as 'Source currency code' with valid examples (USD, EUR, GBP), and to_currency as 'Target currency code' noting the INR default. Examples further reinforce expected formats and common use cases.

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 opens with specific verb ('Get') and resource ('live forex exchange rate'), clearly distinguishing it from stock/crypto siblings. It also specifies scope by detailing the exact data points returned (current rate, day's change, high/low, 52-week range), preventing confusion with simpler price lookup tools.

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 five concrete examples showing valid currency pair combinations, which implicitly guides usage. However, lacks explicit 'when to use' guidance or differentiation from sibling tools like crypto_price. No exclusion criteria or prerequisites mentioned.

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