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. It mentions the tool retrieves 'current' data, implying real-time or recent information, but does not disclose behavioral traits such as data freshness, rate limits, authentication needs, or potential latency. For a tool with zero annotation coverage, this leaves significant gaps in understanding its operation.

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, well-structured sentence that efficiently conveys the tool's purpose without any wasted words. It is front-loaded with the core functionality and appropriately concise for a no-parameter tool.

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 has no parameters, no output schema, and no annotations, the description provides basic purpose but lacks completeness. It does not explain return values (e.g., format of the sentiment ratio), data sources, or limitations, which are important for a tool with no structured fields to compensate.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description appropriately does not add param details, earning a baseline score of 4 for not overloading with unnecessary information.

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 specific verb ('Get') and resource ('current market-wide insider sentiment ratio'), explaining it shows 'buy vs. sell activity' and whether insiders are 'net buyers or sellers'. It effectively distinguishes from siblings like get_congressional_trades or get_insider_profile by focusing on aggregate market sentiment rather than individual trades or profiles.

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 assessing overall market sentiment from insider activity, but does not explicitly state when to use this tool versus alternatives like get_sector_flow or get_trade_heatmap. It provides context but lacks specific guidance on exclusions or prerequisites.

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