Dritan MCP

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

No annotations are provided, so the description carries full burden. It mentions opening a websocket stream and collecting events for a short duration, but lacks details on behavioral traits like whether this is read-only or mutative, authentication needs, rate limits, error handling, or what happens when the stream ends. This is inadequate for a tool with potential real-time data implications.

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 is a single, efficient sentence that front-loads the core action. Every word contributes to understanding the tool's purpose without unnecessary elaboration, making it appropriately sized for its content.

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 tool's complexity (real-time data streaming with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover what events are collected, the output format, error conditions, or prerequisites. This leaves significant gaps for an AI agent to understand how to use the tool effectively.

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%, so the description must compensate. It implies parameters for DEX selection and duration ('short duration'), but doesn't explain the meaning of 'dex', 'durationMs', or 'maxEvents' beyond what the schema provides (e.g., enum values for dex). The description adds minimal semantic context, failing to fully compensate for the coverage gap.

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 action ('Open a DEX websocket stream and collect events') and resource ('DEX websocket stream'), specifying it's for a short duration. However, it doesn't differentiate from sibling tools like 'market_get_snapshot' or 'token_get_aggregated', which might offer alternative ways to get market data.

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. It mentions collecting events 'for a short duration' but doesn't specify scenarios where this is preferable over snapshot-based tools or when not to use it. No explicit alternatives or exclusions are provided.

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