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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'semantic search,' which hints at search behavior, but does not disclose side effects, permissions, rate limits, or any operational characteristics beyond the basic read action. The description is safe and accurate but thin on behavioral detail.

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 is front-loaded with the key action and object. There is no redundant information, and it earns its place without extra 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?

For a search tool with full schema coverage and an output schema, the description is adequately complete. It covers the primary purpose and the parameters are self-explanatory. However, it lacks usage examples or mention of typical scenarios, which would elevate it further, but is not critical given the tool's simplicity.

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 input schema provides 100% coverage of the two parameters ('query' and 'sources'), each with clear descriptions and defaults. The tool description adds no extra meaning or examples beyond the schema, so the baseline of 3 for high schema coverage applies.

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 states a specific verb ('Search'), a clear resource ('ImageKit documentation'), and a distinguishing method ('semantic search'). It is immediately obvious what the tool does and it is distinct from the sibling tool 'transformation_builder', which is about building transformations rather than searching docs.

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 implies usage for searching documentation, but it provides no explicit guidance on when to use this tool versus the sibling tool 'transformation_builder'. There are no exclusions, alternatives, or prerequisites mentioned, leaving it to the agent to infer context from the tool name and purpose.

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