deduplicate_images

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: it's a read-only operation (implied by 'get'), uses semantic analysis via embeddings, and includes optimization logic. However, it lacks details on performance aspects like rate limits or error handling, which would be helpful for a tool with computational complexity.

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 front-loaded with the core purpose in the first sentence and usage guidelines in the second. Both sentences earn their place by adding essential information without redundancy, making it efficient and well-structured for quick comprehension.

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?

Given the tool's complexity (involving embeddings and optimization) and no output schema, the description is mostly complete. It covers purpose, usage, and high-level behavior, but could benefit from mentioning output format (e.g., returned structure) or limitations to fully compensate for the lack of output schema.

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 description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'top-k' and 'semantically unique,' but doesn't provide additional syntax or format details. This meets the baseline for high schema 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?

The description clearly states the tool's purpose with specific verbs ('get top-k semantically unique images') and resources ('images (URLs or base64-encoded)'), and distinguishes it from sibling tools by specifying its unique function of deduplication using Jina CLIP v2 embeddings and submodular optimization, unlike other tools like search_images or deduplicate_strings.

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 explicitly states when to use this tool: 'when you have many visually similar images and want the most diverse subset.' This provides clear context and distinguishes it from alternatives like search_images (for finding images) or deduplicate_strings (for text deduplication), making it easy for an agent to select appropriately.

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