voicestudio_search_api

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, covering the safety profile. The description adds the live-vs-offline distinction, but says nothing about pagination (offset/limit behavior), result format, or freshness (the 'refresh' flag).

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?

Two sentences, front-loaded with the core action and scope, with no filler. The domain enumeration is long but serves the purpose of defining the search surface.

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 6-parameter search tool with no output schema and no schema descriptions, the description establishes what is searched but omits how the filters behave and what the response contains, leaving meaningful gaps for correct invocation.

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?

Six parameters with 0% schema description coverage, and the description supplies no parameter meaning at all — it never explains query, tags, method, limit, offset, or refresh. The enumerated domains loosely hint at what 'tags' might contain but stop short of mapping to any parameter.

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?

States a specific verb (Search) and resource (every live VoiceStudio OpenAPI HTTP operation), then enumerates the covered domains (dubbing, audiobooks, conversion, models, etc.), so an agent knows exactly what surface is being searched. It distinguishes the live operation surface from the 'offline source catalog' but does not explicitly separate itself from siblings like voicestudio_get_operation or voicestudio_call_api.

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 note that the offline source catalog 'is informational only' implies this tool is the right entry point for live search, but there is no explicit when-to-use/when-not or named alternative. Usage is implied rather than stated.

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