search

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

No annotations are provided, and the description is extremely brief, failing to disclose any behavioral traits such as API calls, limitations, side effects, or response format. The agent has no insight into what happens when the tool is invoked.

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 short sentence, making it concise but lacking necessary detail. It earns a middle score because it is not verbose, but the brevity sacrifices completeness.

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 zero annotations, no output schema, and three parameters with no description, the description is severely inadequate. It fails to provide enough context for an agent to use the tool correctly or understand the returned data.

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%, meaning the description adds no explanation for the three parameters (limit, query, service). The agent must infer meaning from parameter names alone, which is insufficient for correct usage.

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 a specific verb ('search') and resource ('media') and includes the intent 'to add', distinguishing it from sibling tools like 'list_services' or 'add_new'. However, it could be more specific about what kind of search (e.g., by title or ID) and what the output is.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical workflows (e.g., search then add_new), or when not to use it.

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