find_images - locate recent screenshots & attachments

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

Annotations already declare readOnly and idempotent. The description adds behavioral context beyond annotations: the specific folders searched (temp, clipboard, Downloads, etc.), newest-first ordering, and how parameters affect results. It doesn't describe return format beyond 'paths', but annotations cover safety profile.

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?

Three sentences: first states purpose and scope, second gives usage context and sibling link, third explains all parameters. No filler, well-structured, front-loaded.

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?

For a read-only search tool with 3 optional params and no output schema, the description covers purpose, usage, parameter behavior, and the relationship to read_context_data. 'Returns their paths, newest first' sufficiently indicates the return value.

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 0% (no property descriptions), so the description carries the full burden. It explains maxResults with default, query as filename filter, and sinceMinutes as time window. This fully compensates for the sparse schema and gives each parameter meaningful semantics.

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 scans multiple specific folders for recent image files and returns their paths newest first. It names the sibling read_context_data and positions this tool as the finder, distinguishing it well.

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?

Explicitly says to use this when the user pastes/drops a screenshot without a file path, and instructs passing returned paths to read_context_data. This provides a clear when-to-use context and points to the next step/alternative.

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