find_files

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

With no annotations, the description carries the burden of disclosure. It conveys the basic behavior of matching by name/glob but does not mention key details like recursion scope, default workspace, or result limits. The schema fills some gaps (e.g., path restriction, pattern semantics), but the description adds little beyond that.

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 a single, well-structured sentence that front-loads the action ('Find files') and then provides usage context. Every word earns its place, with no redundancy or filler.

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?

The tool is relatively simple, and the schema provides detailed parameter descriptions. The description adds enough context for typical usage, though it stops short of explicitly stating the return format or that this is a read-only operation. Overall, it is sufficiently complete for an agent to effectively use the tool.

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 100%, so the baseline is 3. The description adds practical value by giving glob pattern examples ('**/*Service.java', '**/test_*.py'), which illustrate how the 'patterns' parameter should be formatted—enhancing understanding beyond the schema's dry description.

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 function: 'Find files by name or glob pattern' with concrete examples. This distinguishes it from siblings like list_dir (directory listing) and search_code (content search), making the purpose specific and unambiguous.

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 a clear when-to-use guideline: 'Use when you know roughly what a file is called but not where it lives.' It does not explicitly mention when-not-to-use or alternative tools, but the context is sufficient for typical use cases.

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