NiiVue MCP Server

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. While it states the tool searches API methods, it doesn't describe what the search returns (method signatures, documentation snippets, etc.), whether results are paginated, what happens when no matches are found, or any performance characteristics. This leaves significant gaps for an agent to understand the tool's 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 extremely concise - a single sentence that directly states the tool's core function. There's no wasted language or unnecessary elaboration, making it easy to parse and understand at a glance.

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?

For a search tool with 2 parameters (one required), no annotations, and no output schema, the description is inadequate. It doesn't explain what constitutes a successful search, what format results are returned in, how the limit parameter works, or how this tool differs from its siblings. The agent would struggle to use this tool effectively without additional context.

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 for both parameters, the description provides no information about what the 'query' parameter should contain (keywords, exact names, partial matches) or what the 'limit' parameter controls (number of results, pagination). The description mentions searching 'by name or description' which gives minimal context for the query parameter but nothing about format or the limit parameter's purpose.

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 as searching Niivue API methods by name or description, which is a specific verb+resource combination. However, it doesn't distinguish this from its sibling tools like 'search_niivue_docs' or 'get_niivue_api', which appear to perform similar search/retrieval functions in the same domain.

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 its sibling tools. With multiple similar tools available (get_niivue_api, search_niivue_docs, etc.), there's no indication of what makes this tool distinct or when it should be preferred over alternatives.

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