Jesse MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to state whether this is a read-only operation, whether it triggers new backtests or reads existing results, or what constitutes valid 'strategy' identifiers. The mention of 'Returns: Comparative analysis' hints at output but lacks operational context.

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 uses a structured Args/Returns format that is appropriately sized and front-loaded with the core purpose. However, the parameter descriptions ('First strategy name') are somewhat tautological, slightly reducing the value of each sentence.

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?

For a two-parameter tool with an existing output schema, the description covers basic functionality but leaves significant gaps regarding domain specifics—particularly what qualifies as a valid strategy name and whether the comparison requires prior backtesting data. The presence of an output schema excuses detailed return value explanation.

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?

Given 0% schema description coverage, the Args section compensates by labeling 'strategy1' as 'First strategy name' and 'strategy2' as 'Second strategy name.' While this confirms the parameters represent strategy identifiers, it offers minimal domain context (e.g., whether names are case-sensitive, must exist in a specific registry, or follow a particular format).

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 tool 'Compare[s] two strategies to identify best practices' and 'Analyzes performance differences,' providing specific verbs and resources. However, it does not explicitly differentiate from similar sibling tools like 'backtest_compare_timeframes' or 'strategy_analyze_optimization_impact,' leaving potential ambiguity about which comparison tool to select.

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 no guidance on when to use this tool versus alternatives (e.g., 'strategy_analyze_optimization_impact' for single-strategy analysis), nor does it mention prerequisites such as whether strategies must exist or have been backtested prior to comparison.

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