find_files

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

Describes the search mechanism (Spotlight first, fallback) and return format (JSON with metadata or error). Lacks disclosure of permissions needed or side effects, but covers key behavioral aspects beyond no annotations.

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?

Well-structured with Args and Returns sections. Front-loaded with main purpose. Every sentence adds value; no fluff.

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?

Covers all parameters and return type. With output schema present, doesn't need to detail return structure. Lacks error handling or performance limitations, but sufficient for correct invocation.

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?

With 0% schema description coverage, the description provides essential one-line explanations for all 5 parameters, including allowed values for 'kind', making the tool usable.

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 it finds files by name using Spotlight first with Python fallback. Distinguishes from sibling tools like list_directory and search_notes by emphasizing name-based search across a filesystem.

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?

Implies usage for file name searches but does not explicitly say when to prefer this over alternatives like list_directory or when to use different search backends. No 'when not to use' guidance.

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