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

Annotations cover the mutation/safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds genuinely new behavioral context: the call is asynchronous, returns immediately, and the returned source carries a status that later becomes 'ready' after analysis finishes. That polling/eventual-consistency detail is exactly what an agent needs and is not in the annotations. It omits idempotency behavior and failure modes, but the async lifecycle disclosure is valuable.

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, no filler, and the most decision-relevant fact (queued/asynchronous) is front-loaded. Every clause earns its place.

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?

With no output schema, the description does helpfully explain the return shape (the source with a status). However, for a 4-parameter tool with 0% schema coverage and no usage routing against five sibling create/list tools, the definition is not complete enough to guarantee a 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?

Schema description coverage is 0% and the description only vaguely accounts for 'url'. The required brandId and idempotencyKey, plus the optional title, are completely unexplained in either the schema or the description, leaving three of four parameters semantically opaque.

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 gives a specific verb and resource: it queues a URL for scraping and AI analysis, producing a 'source' object. This distinguishes it from create_content_job and create_content_upload_url by implying a URL-scraping ingestion path, though it never names those siblings explicitly.

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?

There is no guidance on when to use this over create_content_job, create_content_upload_url, or create_clip_upload_url, all of which sit in the same creation family. No prerequisites or exclusions are stated, so the agent must infer the routing from the name alone.

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