lynx-mi/lynx-mi-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 'Shows who is buying/selling, volumes, and conviction scores,' which hints at output content, but lacks details on permissions, rate limits, data freshness, or pagination behavior. For a read operation with no annotation coverage, this is insufficient.

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?

Two sentences efficiently convey purpose and key output details without redundancy. The first sentence states the core function, and the second elaborates on data shown, making it front-loaded and waste-free.

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 and no output schema, the description provides basic purpose and output hints but lacks behavioral context (e.g., error handling, data scope). It is minimally adequate for a read tool but incomplete for full agent understanding without structured support.

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%, with clear parameter descriptions in the schema (e.g., ticker as stock symbol, days as lookback). The description adds no additional parameter semantics beyond implying ticker filtering and output fields, so it meets the baseline of 3 without compensating for 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 verb ('Get') and resource ('all insider trading activity for a specific stock ticker'), specifying what data is retrieved (buying/selling, volumes, conviction scores). It distinguishes from siblings like get_congressional_trades (congressional focus) or get_trades_by_insider (insider-based filtering).

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 for ticker-specific insider trading analysis, but does not explicitly state when to use this tool versus alternatives like get_latest_trades (time-based) or search_ticker (broader search). No exclusions or prerequisites are mentioned, leaving some ambiguity in context.

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