search_images

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

No annotations are provided, so the description carries the full burden. It discloses a 3-month time scope, which is useful, but does not specify read-only behavior, authentication needs, rate limits, or other behavioral traits. For a search tool, read-only is assumed but not confirmed.

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 concise with three sentences, no wasted words. It front-loads the core purpose and then provides additional details, making it easy to parse for an AI agent.

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 explains the high-level functionality and search modes, but fails to describe the return format or structure of results. With no output schema, the agent may need to infer what fields are returned (e.g., URLs, metadata). This gap affects completeness.

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 100%, so the parameters are already described. The description adds context about the 3-month limit and global imagery, but does not significantly enhance understanding beyond the schema for individual parameters. Baseline 3 is appropriate.

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 it searches GDELT's Visual Knowledge Graph for news images, with three distinct search modes. It differentiates from the sibling tool 'search_articles' by focusing on images, making the 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 indicates when to use the tool (searching news images) and mentions the three search types, but does not explicitly state when not to use it or provide direct comparison with the sibling tool. However, the distinction between image and article search is implied.

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