search_large_files

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

With no annotations, the description must fully disclose behavior. It fails to mention search scope (e.g., entire drive or current folder), recursion into subfolders, or sorting. Critical operational details are missing, limiting transparency significantly.

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 highly concise: a one-line purpose followed by a parameter list. Every sentence serves a purpose, and the structure is front-loaded with the core action. No waste.

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 description is adequate but missing important context like search scope and recursion behavior. While an output schema exists (reducing need for return value details), the missing scope information is a notable gap for a search 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?

The description adds meaningful context to parameters that the schema lacks. It explains `min_size` with examples ('100mb', '1gb'), clarifies `folder_path` as optional, and notes defaults. However, it could be more precise (e.g., whether extension includes a dot).

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 'Find large files' clearly states the tool's purpose with a specific verb and resource. The focus on file size distinguishes it from sibling tools like 'search_files' and 'search_by_type', making its purpose 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 does not provide any guidance on when to use this tool versus alternatives. Given many sibling tools (e.g., 'search_files', 'search_by_attributes'), the lack of usage context or exclusions makes it harder for an agent to choose appropriately.

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