Jesse MCP Server

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

No annotations provided, so description carries full disclosure burden. States 'Download' implying external API call and data storage, but omits critical behavioral details: whether data overwrites existing candles, append behavior, rate limiting, storage location, or idempotency. Has output schema but doesn't explain the download side effects.

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?

Single sentence of 8 words is appropriately front-loaded with the action verb. However, extreme brevity is inappropriate given zero schema documentation and lack of annotations—more explanatory content is needed to compensate for missing structured metadata.

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?

Despite having an output schema (reducing need to describe return values), the description remains incomplete for a 4-parameter data import tool. Fails to explain the data lifecycle (where candles are stored, how they're accessed by other tools like backtesting_run), which is essential context given the sibling tool ecosystem.

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 has 0% description coverage (4 undocumented parameters). Description mentions 'exchange' implicitly, but fails to specify date formats for start_date/end_date, symbol formatting conventions, or semantics of end_date being null (open-ended range?). Heavy burden on description given schema gap, which it doesn't meet.

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?

States specific action 'Download' and resource 'candle data' with scope 'from exchange via Jesse REST API'. Distinguishes from sibling backtesting tools by specifying data import functionality vs. analysis or execution. However, could explicitly mention this is for backtesting data preparation.

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 no guidance on when to use this tool versus alternatives like backtesting_exchanges (which likely lists available markets). No mention of prerequisites such as exchange connectivity validation or whether data persistence is permanent/temporary.

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