Search C Dance AI prompts

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds useful context by specifying that the gallery is public and free, and by outlining the response contents (previews, thumbnails, source pages). No contradictions with 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?

Two tight sentences with no filler. The search action and resource are front-loaded, return contents are summarized, and the read-only/free note is helpful extra context.

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 tool this is adequate: it names the resource, indicates read-only/free behavior, and summarizes outputs. However, it lacks explicit guidance for the four optional parameters, does not mention pagination or result ordering, and does not route users to sibling tools for single-prompt retrieval or workflow listing.

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% and the description provides no direct guidance on query, limit, language, or featuredOnly. While parameter names are reasonably self-explanatory, the description does not compensate for the complete lack of schema descriptions, especially for language and featuredOnly.

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'), a clear resource (the public C Dance AI Seedance 2.0 prompt gallery), and describes the key return items (previews, video thumbnails, canonical source pages). This clearly distinguishes it from siblings like list_workflows and get_prompt by resource and operation.

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?

Provides clear context: this is for searching a public, read-only, free prompt gallery. It does not explicitly contrast with alternatives like get_prompt or build_video_prompt_brief, but the intended use case is evident and no misleading exclusions are present.

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