search-tools

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

No annotations exist, so description carries full burden. It discloses that the tool returns 'matching tool names + descriptions', implying a read-only query. Does not explicitly state non-destructive nature, but as a search/discovery tool, that is reasonably inferred. Could add note about no side effects.

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?

Two short sentences, each essential. First sentence states purpose and output. Second sentence provides usage guidance. No extraneous text; perfectly front-loaded.

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 no output schema, the description adequately explains what is returned (tool names + descriptions). For a simple search tool with 3 parameters, it is complete enough. Could optionally mention that output is a list or how results are ordered, but not necessary for usability.

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 covers all 3 parameters (100% coverage). Description adds value by clarifying 'query' as natural language for tool discovery across UniFi MCP surface, 'category' as restricting to a specific category, and 'limit' with default 20. This exceeds schema descriptions, which are already good.

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?

Description clearly states verb 'Discover' and resource 'available tools by natural language query'. Unambiguously distinguishes from sibling tools which are specific domain tools (e.g., analyze-site-health, list-devices) by being a general meta-search across all categories.

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 advises using this tool first ('Use this first to navigate the 54-tool surface efficiently'), giving clear context for when to invoke. Does not explicitly state when not to use it, but positive guidance is strong enough for a search tool.

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