Jesse MCP Server

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

No annotations are provided, so the description carries the full burden. While 'Estimate' and 'Analyzes' imply a read-only analytical operation, the description does not explicitly confirm safety, disclose side effects, mention computational cost, or clarify whether this modifies any strategy state.

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?

Uses structured docstring format (Args/Returns) that efficiently conveys input and output expectations. The two summary sentences front-load the core purpose effectively. Slightly odd for MCP description format but wastes no words.

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?

Adequate for a single-parameter analysis tool. The description conceptually covers the return value ('Impact analysis with testing recommendations'), compensating for lack of output schema details. However, missing safety annotations and usage context prevent a higher score.

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?

With 0% schema description coverage, the description compensates by documenting the single parameter as 'Description of the proposed change.' This is minimal (essentially restating the parameter name) but meets the baseline requirement for coverage where the schema fails.

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 'Estimate[s] the impact of a proposed strategy change' and analyzes 'benefits, risks, and testing methodology.' However, it does not differentiate from similar siblings like `strategy_refine`, `strategy_suggest_improvements`, or `optimization_analyze`.

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 the numerous alternatives (e.g., `strategy_optimize_pair_selection`, `optimization_analyze`). No prerequisites or conditions are mentioned despite the presence of many related strategy and optimization tools.

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