Jesse MCP Server

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

No annotations are provided, yet the description discloses no behavioral traits. It does not indicate computational cost, whether results are cached, side effects, or what the output schema contains. The description carries the full burden and fails completely.

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?

At four words, the description is technically brief, but this represents under-specification rather than virtuous conciseness. For a tool with 9 parameters including nested objects, this length is inappropriately small.

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 complexity (9 params, nested objects, 3 required fields) and lack of schema descriptions, the description is radically incomplete. It offers no hint about what constitutes valid input for the required object parameters.

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 0%. The description provides zero compensation for this gap, leaving all 9 parameters undocumented—particularly the three required object parameters (pair, backtest_result_1, backtest_result_2) which have 'additionalProperties: true' and no schema constraints.

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 'Backtest pairs trading strategies' essentially restates the tool name (tautology). While it identifies the domain (pairs trading), it fails to distinguish this tool from siblings like backtest_comprehensive, backtest_monte_carlo, or backtesting_run.

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?

No guidance provided on when to use this tool versus alternatives. Given the numerous backtesting siblings (backtest_comprehensive, backtesting_run, etc.), the absence of selection criteria is a critical gap.

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