Frontrun MCP Server

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it initiates monitoring, has cost implications ($0.10 for standalone users, free for SaaS Pro+), and outputs to 'new follows and convergence data.' However, it misses details like whether tracking is persistent, requires authentication, has rate limits, or what happens on errors. The description adds value but doesn't fully cover behavioral aspects.

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 appropriately sized with two sentences that are front-loaded: the first states the core purpose, and the second adds cost and data context. Every sentence earns its place by providing essential information without redundancy. It could be slightly more structured by separating usage notes, but it's efficient overall.

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 a simple input schema with 100% coverage, the description is moderately complete. It covers purpose, cost, and data output, but lacks details on behavioral traits like persistence, error handling, or integration with sibling tools. For a tool that initiates monitoring with financial implications, more context on operational aspects would improve completeness.

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 100% for the single parameter 'username,' with the schema providing a clear description. The description adds no additional parameter semantics beyond implying the username is for Twitter/X tracking. Since schema coverage is high, the baseline is 3, and the description doesn't compensate with extra details like format examples or constraints.

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's purpose: 'Start monitoring a Twitter/X account' with the specific action of tracking new follows. It distinguishes from siblings by focusing on initiating tracking rather than listing (frontrun_list_tracked), deleting (frontrun_untrack), or analyzing follows (frontrun_new_follows). However, it doesn't explicitly contrast with all siblings like frontrun_create_rule which might also involve monitoring setup.

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 implies usage context by mentioning costs and that tracked data appears in 'new follows and convergence data,' suggesting when to use this for monitoring vs. other tools like frontrun_new_follows for retrieval. However, it lacks explicit guidance on when to choose this over alternatives such as frontrun_create_rule or frontrun_list_tracked, and no exclusions are provided.

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