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 fetching via 'Dritan SDK' but doesn't disclose behavioral traits such as rate limits, authentication needs, error handling, or response format. This is inadequate for a tool with no annotation coverage.

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 key information (fetching token market snapshot). It could be slightly more structured but avoids unnecessary words, making it appropriately concise.

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 no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on behavioral aspects, parameter usage, and return values, making it insufficient for a tool with 2 parameters and multiple data modes.

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 lists data types (price/metadata/risk/first-buyers/aggregated) that map to the 'mode' enum, adding meaning beyond the schema. However, it doesn't explain the 'mint' parameter or provide details on parameter interactions, leaving gaps.

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 ('fetch') and resource ('token market snapshot') with specific data types (price/metadata/risk/first-buyers/aggregated). It distinguishes from siblings like token_get_price and token_get_risk by indicating it fetches multiple data types via a specific SDK, though it doesn't explicitly contrast with all siblings.

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 explicit guidance on when to use this tool versus alternatives like token_get_price or token_get_risk. The description mentions data types but doesn't specify scenarios or exclusions for choosing this over sibling tools, leaving usage context implied.

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