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 describes what the tool does (calculates a score from multiple sources) but lacks details on permissions, rate limits, data freshness, or response format. For a tool with no annotation coverage, this leaves significant gaps in understanding its operational behavior.

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 two sentences that are front-loaded with the core purpose and efficiently explain the score's composition. Every sentence adds value without redundancy, making it appropriately sized and easy to parse.

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 (aggregating multiple data sources) and lack of annotations or output schema, the description is moderately complete. It explains what the tool does but does not cover behavioral aspects like error handling or output details. This is adequate for a read-only tool but could be more comprehensive given the data integration involved.

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 the single parameter 'ticker' documented as 'Stock ticker symbol' in the schema. The description does not add further meaning beyond this, such as format examples or constraints. Baseline 3 is appropriate since the schema handles 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 verb ('Get') and resource ('Nexus political intelligence score for a ticker'), specifying it combines congressional trading activity, lobbying spend, and insider trading into a single risk/opportunity score. This distinguishes it from siblings like get_congressional_trades or get_lobbying_activity, which focus on individual components rather than an aggregated score.

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 by mentioning the score combines specific data sources, suggesting it should be used when a comprehensive political intelligence metric is needed. However, it does not explicitly state when to use this tool versus alternatives like get_conviction_score or get_market_sentiment, nor does it provide exclusions or prerequisites for use.

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