Jesse MCP Server

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

No annotations provided, so description carries full burden. Only discloses return type ('Dict with log entries'). Fails to mention if this retrieves real-time streaming logs or historical batches, pagination behavior, or performance implications of fetching 'all' logs.

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?

Front-loaded one-sentence purpose followed by structured Args/Returns sections. While the docstring format is slightly redundant given schema/output_schema exist, it is justified here due to 0% schema coverage. No extraneous text.

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 2-parameter tool with output schema, but lacks important trading-specific context: whether logs are persistent, if this affects session performance, or the relationship between live vs paper trading logs (given trading_live_paper exists as sibling).

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 coverage is 0%, requiring description to compensate. The Args section provides critical enum values for log_type ('all', 'info', 'error', 'warning') not present in the schema. However, session_id description ('Session ID') is tautological and provides no format guidance.

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?

Clear verb-resource combination ('Get logs from a live trading session') that identifies the specific resource. Distinguishes from other trading_live_* siblings (orders, equity, status) by specifying 'logs', but does not differentiate from logs_analyze_history or logs_strategy_performance.

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 on when to use this tool versus alternatives like logs_analyze_history. No mention of prerequisites (e.g., requiring an active session_id from trading_live_sessions) or when not to use (e.g., for backtesting logs).

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