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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds substantial behavioral context: it ranks results by relevance, lists the exact return fields (id, caption, ocr, image, source, num_likes, date, is_video, rank), and explains the matching source. This goes well beyond the 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?

The description is well-structured: a one-line purpose, a compact bulleted list of return fields, and a clear parameter breakdown. It is front-loaded with the core purpose and every sentence earns its place without redundancy.

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 fully covers the tool's purpose, parameters, and return format. It even includes field names that align with an output schema, making it self-sufficient for an agent to call correctly. The only minor omission is pagination details, but these are not critical for a search tool with a limit parameter.

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 0%, so the description carries the full burden. It thoroughly explains each parameter: query is required and matched against OCR/captions, limit has a range (1-100) and default (20), and days_back semantics (0 = no date filter) are clarified. This adds meaning far beyond the bare schema.

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 opens with 'Search Helium's meme database by text (OCR + caption)', a specific verb-resource-scope statement that clearly differentiates it from sibling tools (which are news, bias, and options focused). It also enumerates the result fields, leaving no ambiguity about what the tool does.

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 explains the search semantics ('Matched against OCR text and captions') and details each parameter, making the intended usage clear. It doesn't explicitly state when NOT to use it or name an alternative, but the sibling set is so different that no exclusion is necessary.

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