search_content

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

No annotations provided, so description carries full burden. Discloses recursive search, defaults, capping, context lines, and return fields. Minor omission: doesn't specify 'matches' format (line numbers/content).

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?

Single-sentence summary followed by bullet-like args. Each parameter earns its place, but could be tightened (e.g., remove 'required' note for pattern, since schema doesn't require it).

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?

No output schema, so description's return fields are helpful. But lacks detail on 'matches' format and what 'truncated' indicates. Still covers core behavior and parameters adequately.

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?

All 7 parameters are explained in description: path as directory/file, pattern as regex, include_hidden for dotfiles, file_glob as glob, case_sensitive, max_matches limit, context_lines. Adds meaning beyond schema (0% coverage).

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?

Clearly states 'Search file contents for a regex pattern (recursive)'. Distinguishes from sibling 'search_glob' (filenames) and is a specific verb+resource.

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?

Implied usage from name and description, but no explicit when-to-use vs siblings like 'search_glob' or 'list_directory'. No exclusions or alternatives mentioned.

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