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

Annotations already declare readOnly, non-destructive, closed-world, so safety is covered. The description adds that content must be UTF-8 and that paths are constrained to an "allowed path" sandbox, which is genuinely extra. It says nothing about result truncation relative to maxResults, depth limits, or whether pattern is interpreted literally or as a regex, which are the behaviors most likely to surprise a caller.

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, constraint-first, and every clause carries information. No filler or restatement of the tool name.

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?

Eight parameters, no output schema, and low schema coverage mean the description should carry more weight than it does. For a file-content search, the interpretation of pattern, the maxResults truncation default, and what a match result looks like are all unaddressed.

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 coverage is only 25%: path and device are documented, six parameters (pattern, maxDepth, ignoreCase, maxResults, filePattern, literalSearch) are not. The description repeats the device guidance already in the schema and never explains that pattern is matched literally by default (literalSearch=true defaults) or that results are capped by default — a materially important distinction the schema does not state.

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 and resource plus scope: search UTF-8 file contents below an allowed path. The word "contents" implicitly separates it from the sibling nymrel_remote_search_files, but the sibling is never named, so an agent must infer the distinction.

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?

"Use this when the user explicitly wants..." gives a usage context and implicitly sets a bar (explicit request) before calling. It never names the obvious alternative (nymrel_remote_search_files) or says when searching names is preferable over contents, so the routing decision is left to inference.

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