FlowCheck Financial API MCP Server

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

No annotations are provided, so the description carries full burden. It mentions the tool exchanges a token for 'permanent access,' hinting at a write operation with lasting effects, but lacks details on authentication requirements, error conditions, rate limits, or what 'permanent access' entails (e.g., scope, revocability). This is a significant gap for a mutation tool with zero annotation coverage.

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 two concise sentences with zero waste: the first states the purpose, and the second provides usage timing. It is front-loaded with the core action and efficiently conveys essential 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?

Given the tool's complexity (a mutation with no annotations and no output schema), the description is adequate but incomplete. It covers purpose and timing well, but lacks behavioral details (e.g., authentication, errors) and output information. For a tool that likely returns an access token or confirmation, the absence of output schema or description of return values is a notable gap.

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 description coverage is 100%, so the schema already documents the single parameter ('public_token') with its description. The description adds minimal value beyond the schema by noting the token comes 'from Link,' but doesn't provide additional syntax, format, or validation details. Baseline 3 is appropriate when the schema handles parameter documentation.

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 the specific action ('Exchange a Plaid public token for permanent access') and resource ('Plaid token'), distinguishing it from siblings like 'flowcheck_create_plaid_link_token' (which creates tokens) and 'flowcheck_connect_*' tools (which connect to other services). It precisely defines the tool's function without ambiguity.

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 explicitly states when to use this tool ('Call this after the user completes Plaid Link in the browser'), providing clear temporal context. It also implies an alternative ('flowcheck_create_plaid_link_token' for obtaining the token first), though it doesn't explicitly name it, the guidance is sufficient for correct sequencing.

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