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 the full burden of behavioral disclosure. It mentions the tool retrieves data based on insider trading activity by volume but does not disclose critical behavioral traits such as whether it requires authentication, rate limits, data freshness, or what the output format looks like (e.g., list of tickers with metrics). This leaves significant gaps for the agent to understand how to invoke and interpret results.

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 concise and front-loaded, consisting of two sentences that efficiently convey the tool's purpose and context without unnecessary details. Every sentence adds value: the first defines the action and resource, and the second provides additional context on what it shows, making it easy for an agent to parse quickly.

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 complexity of a data retrieval tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., authentication, rate limits) and does not explain the return values or structure, which is critical for the agent to use the tool effectively. The description provides basic purpose but fails to address key contextual needs for invocation and interpretation.

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?

The input schema has 100% description coverage for the single parameter 'days,' so the schema already documents it fully. The description does not add any parameter-specific information beyond what the schema provides, such as default behavior or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description does not compensate but also does not detract.

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 with a specific verb ('Get') and resource ('stocks with the highest insider trading activity'), and distinguishes it from siblings by focusing on volume-based ranking of insider interest. It explicitly mentions 'by volume' and 'most insider interest right now,' which differentiates it from tools like get_insider_rank or get_leaderboard that might use other metrics.

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 ('Shows which tickers have the most insider interest right now') but does not explicitly state when to use this tool versus alternatives like get_insider_rank or get_latest_trades. It provides a general purpose but lacks specific guidance on exclusions or comparisons with sibling tools, leaving some ambiguity for the agent.

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