Search Actors

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

With no annotations provided, the description carries the full burden. It discloses the return shape, the empty-search behavior, and clarifies the domain of Actors. It doesn't address possible pagination or matching semantics, but for a safe search operation this is reasonably transparent.

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?

Three short sentences with no filler. The action, return value, use case, and special search behavior are all communicated efficiently, and the most important operational detail ('start here') is front-loaded.

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 simple search/list tool, the description covers the main invocation concerns: what it searches, what it returns, and how to retrieve all entries. A small gap is that the effect of 'limit' on the result set is only implicit in the schema, and there is no mention of pagination even though no output schema exists.

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 schema already describes the 'search' parameter with examples, so the description's added context focuses on the empty-search case. The 'limit' parameter is left to schema constraints with no behavioral explanation, so the description partially compensates for the 50% schema coverage but doesn't fully close the gap.

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'), a specific resource ('available Actors'), and defines Actors as 'scrapers and data collectors.' It also states the exact return fields (id, title, description), which distinguishes it from sibling tools like call-actor or fetch-actor-details.

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 gives explicit guidance on when to start here ('when you need to extract data from the web') and how to list everything ('pass an empty search'). It does not explicitly mention when not to use it or name alternative sibling tools, so it stops short of a 5.

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