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 states the tool retrieves a detailed profile, implying a read-only operation, but does not disclose any behavioral traits such as rate limits, authentication requirements, data freshness, or potential errors. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 the core purpose ('Get a detailed profile of a specific insider') and lists key components without unnecessary elaboration. It is appropriately sized for the tool's complexity, with no wasted words, though it could be slightly more structured by separating usage context.

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's complexity (detailed profile with multiple data points), lack of annotations, and no output schema, the description is incomplete. It does not explain what the return values include beyond high-level categories, nor does it cover behavioral aspects like performance or limitations. For a tool with rich expected output and no structured support, the description should provide more context to be fully helpful.

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, with the parameter 'insider_name' documented as 'Full name of the insider'. The description adds no additional meaning beyond this, as it does not explain parameter semantics like format constraints or examples. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema already handles the parameter documentation adequately.

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: 'Get a detailed profile of a specific insider' with specific components like trading history, average trade size, sectors, and behavioral patterns. It distinguishes itself from siblings like get_insider_network or get_insider_rank by focusing on a comprehensive individual profile rather than network connections or rankings. However, it could be more specific about what distinguishes it from get_trades_by_insider, which might overlap in trading history.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when to choose this over siblings like search_insider, get_trades_by_insider, or get_insider_network, nor does it specify any prerequisites or exclusions. The context is implied (e.g., when detailed insider info is needed), but explicit usage guidelines are absent.

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