Invoke Clip Create From Item

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

Description adds significant behavioral context beyond annotations: explains it's a money path (reserves CU), idempotency key parity, and that retries return first response without duplication. No contradiction with annotations (idempotentHint=true). Minor gap: no mention of side effects beyond job creation.

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?

Single dense sentence conveys core purpose and critical behavioral nuances without extraneous words. Front-loaded with key action.

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?

Despite complexity (money path, idempotency, job dispatch), description lacks return value explanation, parameter details, and input specification (e.g., how to identify the item). Minimal schema output exacerbates gaps.

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?

Input schema has 2 parameters with 0% description coverage; description does not explain x-api-key or body meaning, leaving the agent to guess. No compensation for absent schema documentation.

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?

Description uses specific verb+resource ('Create + dispatch a cog_clip job from an item') and clearly distinguishes from sibling clip tools (e.g., clip.job.get, clip.jobs.list) by focusing on creation and dispatch.

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?

Description provides important context (money path, reserves CU, idempotency key parity) but lacks explicit guidance on when to use vs alternatives (e.g., processing.create_and_dispatch) or when not to use.

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