seeany_refine_prompt

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

Annotations indicate non-read-only, open-world, non-destructive behavior, and the description does not contradict them. It adds the core behavior of transforming a rough prompt into a refined one, but it does not explain how action, extra_context, or reference_asset_ids influence the result, nor what the returned output looks like.

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 front-loaded sentence with no filler. It efficiently communicates the tool's purpose and transformation without wasting words.

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 four parameters, no output schema, and sibling tools for image generation, the description is too thin. It does not explain the parameters, when to prefer this over generation tools, or what the refined prompt output contains, leaving important gaps for an AI agent.

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%, so the description must compensate for the four undocumented parameters. It only indirectly clarifies the 'prompt' parameter and leaves 'action', 'extra_context', and 'reference_asset_ids' unexplained, including the meaning of the enum values.

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 states a clear verb ('refine') and resource ('SeeAny AI prompt refinement'), and explains the transformation from a rough product-image request to a production-ready prompt. It does not explicitly distinguish itself from siblings like seeany_generate_product_image, but the purpose is still clear.

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 clearly implies when to use the tool: when the user has a rough product-image request and needs a refined, production-ready prompt. It does not mention alternatives or exclusions, but the context is sufficient for an agent to select it over image-generation or asset-management tools.

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