Search files inside the Nextcloud workspace

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

Annotations already declare readOnlyHint, destructiveHint=false, openWorldHint=false; the description reinforces the closed-world profile ('bounded account search') and adds a genuinely new trait: only filenames are matched, not file contents, which tells the agent when to fall back to read_text_file. It does not mention depth or result-count bounding behavior, which limits it to a 4.

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, front-loaded with the core action and scope, with no filler. The second sentence is slightly redundant with the first for a reader who already knows Nextcloud, but it earns its place as a disambiguation cue.

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?

An output schema exists so return values need no explanation, and the safety profile is covered by annotations. But with 4 undocumented parameters and no explanation of query matching semantics, an agent cannot confidently set path, max_depth, or max_results from this definition alone.

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 0% across four parameters, so the description carries the full burden—yet it says nothing about what 'query' matches (substring, case sensitivity, globs), what 'path' scopes relative to the workspace root, or what max_depth and max_results control. Only the workspace-root scope is hinted at.

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?

States a specific verb (search) and a specific resource and scope: filenames only, inside the user's connected private Nextcloud workspace root. It explicitly rules out public web search and other destinations, though it never distinguishes itself from the sibling list_files, which an agent could plausibly choose instead.

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 second sentence gives negative usage guidance—it is 'not public web search or a search of other destinations'—which narrows the context. However, there is no positive guidance on when to pick this over list_files or get_file_info, and no preconditions or exclusions relative to actual siblings.

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