nexusfeed-mcp

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden and does an excellent job disclosing behavioral traits: state-specific implementation details (TX requires captcha, NY only active licenses, FL searches all board types), compliance requirements (extraction_confidence and source_timestamp thresholds), and server-side limitations (city/county/zip/license_status filters not applied server-side).

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?

Front-loaded with core purpose, then usage guidelines, then implementation details. Every sentence adds value, though the state-specific details paragraph is somewhat dense. Could be slightly more structured but remains efficient.

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 (9 parameters, no annotations, state-specific implementations, compliance requirements) and presence of an output schema, the description is remarkably complete. It covers purpose, usage context, behavioral constraints, parameter semantics, and important limitations without needing to explain return values.

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?

With 0% schema description coverage, the description compensates well by explaining what the search matches against (business name, owner name, address) and mentioning additional filters (city, county, zip, license_status) even though they're not applied server-side. However, it doesn't fully explain all 9 parameters' purposes.

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 searches a US state ABC board database for liquor licenses using specific search criteria (business name, owner name, address). It distinguishes from sibling tools by specifying it's for searching licenses rather than listing states or looking up individual licenses.

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?

Explicitly states when to use this tool: 'before approving a distributor order, binding an insurance policy, or onboarding a merchant to verify they hold a valid liquor license.' Also provides important exclusions about when results are valid for compliance decisions based on verifiability block criteria.

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