search_ugc_actors

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

Beyond the readOnlyHint annotation, the description discloses materialization requirements and the rejection behavior for missing skill grants. These are significant behavioral traits that help the agent anticipate outcomes and dependencies.

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 three short sentences, front-loaded with the primary action. No redundancy or filler, every sentence adds value.

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 covers the core behavior and critical prerequisites, but with 7 optional parameters and no output schema, it lacks details on filtering, pagination, and return values. The completeness is adequate for a simple search but not fully fleshed out.

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?

With 7 parameters and 0% schema description coverage, the description must compensate but provides no details on query, gender, region, ageGroup, category, page, or pageSize. This leaves the agent without guidance on how to properly invoke the tool.

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 the approved UGC actor catalog, using a specific verb and resource. This distinguishes it from sibling search tools like search_project_assets or search_gallery, which have different domains.

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 explicitly instructs to call run_skill first and warns that the tool rejects direct calls without the active skill grant/run descriptor. This provides strong usage context, including a prerequisite and a condition for successful invocation.

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